{"metadata": {"vulnerability": "CVE-2026-98974", "count": 18, "kinds": {"milestone": 7, "sighting": 1, "kev": 0, "other": 10}}, "data": [{"timestamp": "2026-09-25T10:25:14.383Z", "date_only": false, "value": "2026-09-25T10:25:14.383Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-98974", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-10-23T12:19:47.424Z", "date_only": false, "value": "2026-10-23T12:19:47.424Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-98974", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-23T13:17:00Z", "date_only": false, "value": "2026-10-23T13:17:00Z", "kind": "milestone", "label": "Published", "source": "osv_ubuntu \u00b7 UBUNTU-CVE-2026-98974", "record": "UBUNTU-CVE-2026-98974", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-10-23T13:17:19Z", "date_only": false, "value": "2026-10-23T13:17:19Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-2G9R-FC27-29GX", "record": "GHSA-2G9R-FC27-29GX", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-10-23T13:17:19.013Z", "date_only": false, "value": "2026-10-23T13:17:19.013", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-98974", "record": "FKIE_CVE-2026-98974", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-10-23T13:22:40.075Z", "date_only": false, "value": "2026-10-23T13:22:40.075250Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117490434660008812", "record": "CVE-2026-98974", "field": "creation_timestamp", "uuid": "88713602-1177-46f2-a7d6-c8e4e505d481", "content": "CVE-2026-98974 xfs: fix exchange-range-to-eof file size exchange In the Linux kernel, the following vulnerability has been resolved:\nxfs: fix exchange-range-to-eof file size exchange\nNorbert Szetei posted a patch containing an incomplete description of abug in XFS_IOC_EXCHANGE_RANGE's TO_EOF flag.  The bug tricksexchange-range into modifying a file so that it has shared blocksstarting beyond EOF, which is never allowed because files never havewritten data beyond EOF, and you can only share written data blocks.This is key to all the incorrect behavior that follows.\nEventually I got from Norbert a description of what's going wrong:\n> Fair. Here it is with physical block numbers, 4k blocks. peer is the file> that gets rewritten and file1 is the one that ends up with the flag> cleared.>> Start, nothing shared:>>\tpeer size 4096   -> [100]>\tfile1 size 12288 -> [200] [201] [202]>\tdonor1 size 4096 -> [300]>\tdonor2 size 4096 -> [400]>> 1. FICLONERANGE peer's block into file1's middle slot:>>\tpeer size 4096   -> [100]>\tfile1 size 12288 -> [200] [100] [202] reflink flag set>                             ^^^^^ both files own block 100>> 2. XFS_IOC_EXCHANGE_RANGE file1 against donor1, file1_offset 0,> file2_offset 8192, length 0, TO_EOF. One block is exchanged, and the sizes> are exchanged with it:>>\tfile1 size 4096   -> [200] [100] [300] reflink flag set>                              ^^^^^^^^^^^ still owned, now past the size>\tdonor1 size 12288 -> [202]>> file1 says it is one block long while it still owns three. Nothing was> unmapped. file2_offset is block 2, so this exchange cannot clear a flag.>> 3. XFS_IOC_EXCHANGE_RANGE file1 against donor2, both offsets 0, length 4096.> By i_disk_size this is two one-block files exchanging everything, so> xmi_can_exchange_reflink_flags() agrees and the flag is cleared:>>\tfile1 size 4096   -> [400] [100] [300] reflink flag CLEARED>\tdonor2 size 4096  -> [200]>> Block 100 is still shared with peer.>> 4. pwrite(file1, 4096, 4096), which is file1's second slot, block 100.> xfs_is_cow_inode(file1) is false, so no CoW:>>\tpeer size 4096 -> [100] same block, new contents>> Block 100 is the only one that matters here. PoC below, it reads a file> called peer in the current directory. The filesystem needs reflink and> exchange-range, which mkfs.xfs 7.x turns on by default.\nSo yes, TO_EOF is screwing up the file size even if it's actuallyexchanging the data block correctly.  The following is the intendedbehavior of XFS_EXCHANGE_RANGE_TO_EOF, as described by its manpage:\n\"Ignore the length parameter.  All bytes in file1_fd from file1_offset to EOF are moved to file2_fd, and file2's size is set to (file2_offset+(file1_length-file1_offset)).  Meanwhile, all bytes in file2 from file2_offset to EOF are moved to file1 and file1's size is set to (file1_offset+(file2_length-file2_offset)).\"\nIn other words, if we only exchange a portion of the file data, then weshould only exchange the portion of the file size that relates to theexchanged data.  Unfortunately, the code swaps the ondisk file size andthe incore file sizes, which is incorrect if the caller passes in anonzero offset.\nHaving confused the file sizes, the PoC uses a second exchange-rangecall on what looks like a non-reflinked single-block file.  Because thefile size is set incorrectly, exchange-range thinks it's exchanging thefull contents of two files and clears the reflink flag on the brokenfile.  That enables an extending write of the broken file to rewrite theshared block that's just past EOF.  This has become known colloquiallyas refluxfs.\nOnce the file sizes are set correctly, the second exchange-range nolonger thinks that it's doing a full-contents swap, so it won't clearthe reflink flag on either of its file arguments.\nNorbert followed up to an earlier version of this patch with a secondcomplaint about us not handling the i_disk_size state correctly:\n> The offsets are bounded against the incore i_size but subtracted from>---truncated---\nhttps://www.cve.org/CVERecord?id=CVE-2026-98974https://git.kernel.org/stable/c/b361d32b884f8ddcb9bad5d99b69eece648f8e43https://git.kernel.org/stable/c/cf32eb20dfacfd2e92ce86ba1fece9ae5f98a7d8https://git.kernel.org/stable/c/952b5c99a840c2bff1f6645fd5e06e1db6ec2623https://git.kernel.org/stable/c/7dfb218c829c1acb626e0fe92c5fddb9a26a03e9#kernel #Linux#CVE_2026_98974#bot", "url": "https://infosec.exchange/users/cve/statuses/117490434660008812"}, {"timestamp": "2026-10-23T15:31:33Z", "date_only": false, "value": "2026-10-23T15:31:33Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-2G9R-FC27-29GX", "record": "GHSA-2G9R-FC27-29GX", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-10-24T01:10:32Z", "date_only": false, "value": "2026-10-24T01:10:32.000Z", "kind": "other", "label": "Advisory revision", "source": "csaf_microsoft \u00b7 MSRC_CVE-2026-98974", "record": "MSRC_CVE-2026-98974", "field": "document.tracking.revision_history.0.date", "linked_record": true}, {"timestamp": "2026-10-24T01:10:32Z", "date_only": false, "value": "2026-10-24T01:10:32.000Z", "kind": "milestone", "label": "Published", "source": "csaf_microsoft \u00b7 MSRC_CVE-2026-98974", "record": "MSRC_CVE-2026-98974", "field": "document.tracking.initial_release_date", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-10-24T01:10:32Z", "date_only": false, "value": "2026-10-24T01:10:32.000Z", "kind": "other", "label": "Updated", "source": "csaf_microsoft \u00b7 MSRC_CVE-2026-98974", "record": "MSRC_CVE-2026-98974", "field": "document.tracking.current_release_date", "linked_record": true}, {"timestamp": "2026-10-24T07:00:42.696Z", "date_only": false, "value": "2026-10-24T07:00:42.696Z", "kind": "other", "label": "Document generated", "source": "csaf_microsoft \u00b7 MSRC_CVE-2026-98974", "record": "MSRC_CVE-2026-98974", "field": "document.tracking.generator.date", "linked_record": true}, {"timestamp": "2026-10-24T14:09:44.115Z", "date_only": false, "value": "2026-10-24T14:09:44.115Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-98974", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-10-24T14:09:44.115Z", "date_only": false, "value": "2026-10-24T14:09:44.115Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-98974", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-10-24T14:16:49.923Z", "date_only": false, "value": "2026-10-24T14:16:49.923", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-98974", "record": "FKIE_CVE-2026-98974", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-10-24T15:32:48Z", "date_only": false, "value": "2026-10-24T15:32:48Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-2G9R-FC27-29GX", "record": "GHSA-2G9R-FC27-29GX", "field": "modified", "linked_record": true}, {"timestamp": "2026-10-28T06:07:53.994Z", "date_only": false, "value": "2026-10-28T06:07:53.99411Z", "kind": "milestone", "label": "Published", "source": "osv_bellsoft \u00b7 BELL-CVE-2026-98974", "record": "BELL-CVE-2026-98974", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-10-30T06:30:05Z", "date_only": false, "value": "2026-10-30T06:30:05Z", "kind": "other", "label": "Updated", "source": "osv_ubuntu \u00b7 UBUNTU-CVE-2026-98974", "record": "UBUNTU-CVE-2026-98974", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-03T06:23:55.305Z", "date_only": false, "value": "2026-11-03T06:23:55.305630Z", "kind": "other", "label": "Updated", "source": "osv_bellsoft \u00b7 BELL-CVE-2026-98974", "record": "BELL-CVE-2026-98974", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-04T15:28:55.297Z", "anchors": {"origin": {"timestamp": "2026-10-23T12:19:47.424Z", "date_only": false, "value": "2026-10-23T12:19:47.424Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-98974", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-10-23T12:19:47.424Z", "date_only": false, "value": "2026-10-23T12:19:47.424Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-98974", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 1048147.873137, "hours": 291.1521869825, "days": 12.131341124270833, "min_seconds": 1048147.873137, "max_seconds": 1048147.873137, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-10-23T12:19:47.424Z", "date_only": false, "value": "2026-10-23T12:19:47.424Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-98974", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-04T15:28:55.297Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}