CVE-2026-80530

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-80530", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-08-26T14:34:25.764Z", "datePublished": "2026-08-26T14:37:07.990Z", "dateUpdated": "2026-10-16T19:26:24.966Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-27T05:01:24.159Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN\n\nWhen exchanging two full-file ranges, xmi_can_exchange_reflink_flags()\ncan move the reflink inode flag from the file that currently has it to\nthe other file, as long as exactly one side is marked. This assumes\nthat the file contents, and therefore all shared extents, are exchanged.\n\nThat assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set.\nxfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings\nfrom file1, so an exchange can complete without moving every mapping\nthat the earlier flag-swap decision accounted for. In that case the\npost-operation cleanup can clear the reflink flag from an inode that\nstill owns shared written extents. Later writes then take the\nnon-reflink write path and may update blocks that should still have\nbeen protected by CoW, which shows up as data corruption between\nreflink-related files.\n\nFix this by disabling the reflink flag exchange whenever\nXFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still\nproceed; the conservative outcome is that both inodes keep the reflink\nflag. The regular reflink flag cleanup path can drop the extra flag\nlater once the inode no longer has shared extents."}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "baseScore": 7.1, "baseSeverity": "HIGH"}, "scenarios": [{"lang": "en", "value": "AV:L - The flaw is only reachable via xfs_ioc_exchange_range()/xfs_ioc_commit_range() through XFS_IOC_EXCHANGE_RANGE or XFS_IOC_COMMIT_RANGE ioctl on open XFS file descriptors; there is no nfsd, ksmbd, or network packet path to xfs_exchmaps_clear_reflink().\nAC:L - A local attacker can craft reflinked files with hole/unwritten mappings, open both files read-write, and call exchange-range with XFS_EXCHANGE_RANGE_FILE1_WRITTEN|TO_EOF to deterministically skip mappings and trigger incorrect post-op reflink-flag clearing.\nPR:L - XFS_IOC_EXCHANGE_RANGE has no CAP_SYS_ADMIN gate and only requires DAC write on both exchanged files plus read access to reflink-clone a victim file; unprivileged users on shared multi-tenant XFS mounts meet this without init-namespace root.\nUI:N - Exploitation requires only the attacker's own ioctl calls on files they control; no separate victim must mount media, click prompts, or perform actions beyond storing readable data the attacker reflinks.\nS:U - Impact is on-disk data corruption or commingling between reflink-linked files within the same host kernel/filesystem authority; it does not cross VM, container network, or IOMMU boundaries like a hypervisor escape.\nC:H - Clearing the reflink inode flag while shared written extents remain breaks CoW isolation, so subsequent non-reflink writes can commingle or overwrite blocks still linked to other users' reflink clones, leaking data CoW should have kept private.\nI:H - After the incorrect reflink-flag clear, writes take the non-reflink path and directly modify shared storage blocks, letting an attacker corrupt content in other users' reflink-linked files without write permission to those inodes.\nA:N - The failure is logical metadata mishandling causing cross-file data corruption; it does not trigger kernel oops, panic, BUG_ON, or hang, and the fix commit describes only data corruption between reflink-related files, not system unavailability."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/xfs/libxfs/xfs_exchmaps.c"], "versions": [{"version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "2efbd8890b53f4756fdc7b0ef346fa514ffb7d66", "status": "affected", "versionType": "git"}, {"version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "0f27b22343b63e10773e6781344640c2c753eec3", "status": "affected", "versionType": "git"}, {"version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "03c9c9116e6da641424681f705698d7f5e2128e0", "status": "affected", "versionType": "git"}, {"version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "b2d5a81dae385333f9734910277fbf94c78bd17f", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/xfs/libxfs/xfs_exchmaps.c"], "versions": [{"version": "6.10", "status": "affected"}, {"version": "0", "lessThan": "6.10", "status": "unaffected", "versionType": "semver"}, {"version": "6.12.105", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.18.46", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.1.10", "lessThanOrEqual": "7.1.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "6.12.105"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "6.18.46"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "7.1.10"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10", "versionEndExcluding": "7.2"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/2efbd8890b53f4756fdc7b0ef346fa514ffb7d66"}, {"url": "https://git.kernel.org/stable/c/0f27b22343b63e10773e6781344640c2c753eec3"}, {"url": "https://git.kernel.org/stable/c/03c9c9116e6da641424681f705698d7f5e2128e0"}, {"url": "https://git.kernel.org/stable/c/b2d5a81dae385333f9734910277fbf94c78bd17f"}], "title": "xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN", "x_generator": {"engine": "bippy-1.2.0"}}, "adp": [{"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/09/03/1"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2026-09-03T15:07:45.454Z"}}, {"metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-80530", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-10-16T19:16:41.654817Z"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-16T19:26:24.966Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/09/03/1"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2026-09-03T15:07:45.454Z"}}, {"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-80530", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-10-16T19:16:41.654817Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-16T19:16:42.759Z"}}], "cna": {"title": "xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN", "metrics": [{"cvssV3_1": {"version": "3.1", "baseScore": 7.1, "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"}, "scenarios": [{"lang": "en", "value": "AV:L - The flaw is only reachable via xfs_ioc_exchange_range()/xfs_ioc_commit_range() through XFS_IOC_EXCHANGE_RANGE or XFS_IOC_COMMIT_RANGE ioctl on open XFS file descriptors; there is no nfsd, ksmbd, or network packet path to xfs_exchmaps_clear_reflink().\nAC:L - A local attacker can craft reflinked files with hole/unwritten mappings, open both files read-write, and call exchange-range with XFS_EXCHANGE_RANGE_FILE1_WRITTEN|TO_EOF to deterministically skip mappings and trigger incorrect post-op reflink-flag clearing.\nPR:L - XFS_IOC_EXCHANGE_RANGE has no CAP_SYS_ADMIN gate and only requires DAC write on both exchanged files plus read access to reflink-clone a victim file; unprivileged users on shared multi-tenant XFS mounts meet this without init-namespace root.\nUI:N - Exploitation requires only the attacker's own ioctl calls on files they control; no separate victim must mount media, click prompts, or perform actions beyond storing readable data the attacker reflinks.\nS:U - Impact is on-disk data corruption or commingling between reflink-linked files within the same host kernel/filesystem authority; it does not cross VM, container network, or IOMMU boundaries like a hypervisor escape.\nC:H - Clearing the reflink inode flag while shared written extents remain breaks CoW isolation, so subsequent non-reflink writes can commingle or overwrite blocks still linked to other users' reflink clones, leaking data CoW should have kept private.\nI:H - After the incorrect reflink-flag clear, writes take the non-reflink path and directly modify shared storage blocks, letting an attacker corrupt content in other users' reflink-linked files without write permission to those inodes.\nA:N - The failure is logical metadata mishandling causing cross-file data corruption; it does not trigger kernel oops, panic, BUG_ON, or hang, and the fix commit describes only data corruption between reflink-related files, not system unavailability."}]}], "affected": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "2efbd8890b53f4756fdc7b0ef346fa514ffb7d66", "versionType": "git"}, {"status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "0f27b22343b63e10773e6781344640c2c753eec3", "versionType": "git"}, {"status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "03c9c9116e6da641424681f705698d7f5e2128e0", "versionType": "git"}, {"status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "lessThan": "b2d5a81dae385333f9734910277fbf94c78bd17f", "versionType": "git"}], "programFiles": ["fs/xfs/libxfs/xfs_exchmaps.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.10"}, {"status": "unaffected", "version": "0", "lessThan": "6.10", "versionType": "semver"}, {"status": "unaffected", "version": "6.12.105", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.46", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.1.10", "versionType": "semver", "lessThanOrEqual": "7.1.*"}, {"status": "unaffected", "version": "7.2", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["fs/xfs/libxfs/xfs_exchmaps.c"], "defaultStatus": "affected"}], "references": [{"url": "https://git.kernel.org/stable/c/2efbd8890b53f4756fdc7b0ef346fa514ffb7d66"}, {"url": "https://git.kernel.org/stable/c/0f27b22343b63e10773e6781344640c2c753eec3"}, {"url": "https://git.kernel.org/stable/c/03c9c9116e6da641424681f705698d7f5e2128e0"}, {"url": "https://git.kernel.org/stable/c/b2d5a81dae385333f9734910277fbf94c78bd17f"}], "x_generator": {"engine": "bippy-1.2.0"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN\n\nWhen exchanging two full-file ranges, xmi_can_exchange_reflink_flags()\ncan move the reflink inode flag from the file that currently has it to\nthe other file, as long as exactly one side is marked. This assumes\nthat the file contents, and therefore all shared extents, are exchanged.\n\nThat assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set.\nxfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings\nfrom file1, so an exchange can complete without moving every mapping\nthat the earlier flag-swap decision accounted for. In that case the\npost-operation cleanup can clear the reflink flag from an inode that\nstill owns shared written extents. Later writes then take the\nnon-reflink write path and may update blocks that should still have\nbeen protected by CoW, which shows up as data corruption between\nreflink-related files.\n\nFix this by disabling the reflink flag exchange whenever\nXFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still\nproceed; the conservative outcome is that both inodes keep the reflink\nflag. The regular reflink flag cleanup path can drop the extra flag\nlater once the inode no longer has shared extents."}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.12.105", "versionStartIncluding": "6.10"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.18.46", "versionStartIncluding": "6.10"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "7.1.10", "versionStartIncluding": "6.10"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "7.2", "versionStartIncluding": "6.10"}], "operator": "OR"}]}], "providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-27T05:01:24.159Z"}}}, "cveMetadata": {"cveId": "CVE-2026-80530", "state": "PUBLISHED", "dateUpdated": "2026-10-16T19:26:24.966Z", "dateReserved": "2026-08-26T14:34:25.764Z", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "datePublished": "2026-08-26T14:37:07.990Z", "assignerShortName": "Linux"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["fs/xfs/libxfs/xfs_exchmaps.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "2efbd8890b53f4756fdc7b0ef346fa514ffb7d66", "status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "versionType": "git"}, {"lessThan": "0f27b22343b63e10773e6781344640c2c753eec3", "status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "versionType": "git"}, {"lessThan": "03c9c9116e6da641424681f705698d7f5e2128e0", "status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "versionType": "git"}, {"lessThan": "b2d5a81dae385333f9734910277fbf94c78bd17f", "status": "affected", "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["fs/xfs/libxfs/xfs_exchmaps.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.10"}, {"lessThan": "6.10", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "6.12.*", "status": "unaffected", "version": "6.12.105", "versionType": "semver"}, {"lessThanOrEqual": "6.18.*", "status": "unaffected", "version": "6.18.46", "versionType": "semver"}, {"lessThanOrEqual": "7.1.*", "status": "unaffected", "version": "7.1.10", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.2", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN\n\nWhen exchanging two full-file ranges, xmi_can_exchange_reflink_flags()\ncan move the reflink inode flag from the file that currently has it to\nthe other file, as long as exactly one side is marked. This assumes\nthat the file contents, and therefore all shared extents, are exchanged.\n\nThat assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set.\nxfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings\nfrom file1, so an exchange can complete without moving every mapping\nthat the earlier flag-swap decision accounted for. In that case the\npost-operation cleanup can clear the reflink flag from an inode that\nstill owns shared written extents. Later writes then take the\nnon-reflink write path and may update blocks that should still have\nbeen protected by CoW, which shows up as data corruption between\nreflink-related files.\n\nFix this by disabling the reflink flag exchange whenever\nXFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still\nproceed; the conservative outcome is that both inodes keep the reflink\nflag. The regular reflink flag cleanup path can drop the extra flag\nlater once the inode no longer has shared extents."}], "id": "CVE-2026-80530", "lastModified": "2026-10-16T20:17:57.880", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "NONE", "baseScore": 7.1, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 5.2, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-80530", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-10-16T19:16:41.654817Z", "version": "2.0.3"}}]}, "published": "2026-08-26T15:17:06.990", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/03c9c9116e6da641424681f705698d7f5e2128e0"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/0f27b22343b63e10773e6781344640c2c753eec3"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/2efbd8890b53f4756fdc7b0ef346fa514ffb7d66"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/b2d5a81dae385333f9734910277fbf94c78bd17f"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "url": "http://www.openwall.com/lists/oss-security/2026/09/03/1"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN", "id": "2524492", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2524492"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.0", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "status": "draft"}, "cwe": "CWE-911", "details": ["A flaw was found in the Linux kernel's XFS filesystem. When performing file range exchanges with the XFS_EXCHMAPS_INO1_WRITTEN flag set, the reflink flag can be prematurely cleared from an inode that still manages shared written data. This can lead to data corruption between files that share data through the reflink mechanism, as subsequent writes may bypass Copy-on-Write (CoW) protection."], "name": "CVE-2026-80530", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2026-08-26T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-80530\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-80530\nhttps://lore.kernel.org/linux-cve-announce/2026082603-CVE-2026-80530-4a96@gregkh/T"], "threat_severity": "Moderate"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[966ceafc7a437105ecfe1cadb3747b2965a260ca,2efbd8890b53f4756fdc7b0ef346fa514ffb7d66)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[966ceafc7a437105ecfe1cadb3747b2965a260ca,0f27b22343b63e10773e6781344640c2c753eec3)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[966ceafc7a437105ecfe1cadb3747b2965a260ca,03c9c9116e6da641424681f705698d7f5e2128e0)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[966ceafc7a437105ecfe1cadb3747b2965a260ca,b2d5a81dae385333f9734910277fbf94c78bd17f)"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}, {"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "6.10"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[0,6.10)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.12.105,6.13.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.18.46,6.19.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[7.1.10,7.2.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[7.2,*]"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}], "created": "2026-08-26T16:45:08.202501+00:00", "updated": "2026-08-27T08:15:05.749980+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}