CVE-2026-43075
What it is
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix out-of-bounds write in ocfs2_write_end_inline KASAN reports a use-after-free write of 4086 bytes in ocfs2_write_end_inline, called from ocfs2_write_end_nolock during a copy_file_range splice fallback on a corrupted ocfs2 filesystem mounted on a loop device. The actual bug is an out-of-bounds write past the inode block buffer, not a true use-after-free. The write overflows into an adjacent freed page, which KASAN reports as UAF. The root cause is that ocfs2_try_to_write_inline_data trusts the on-disk id_count field to determine whether a write fits in inline data. On a corrupted filesystem, id_count can exceed the physical maximum inline data capacity, causing writes to overflow the inode block buffer. Call trace (crash path): vfs_copy_file_range (fs/read_write.c:1634) do_splice_direct splice_direct_to_actor iter_file_splice_write ocfs2_file_write_iter generic_perform_write ocfs2_write_end ocfs2_write_end_nolock (fs/ocfs2/aops.c:1949) ocfs2_write_end_inline (fs/ocfs2/aops.c:1915) memcpy_from_folio <-- KASAN: write OOB So add id_count upper bound check in ocfs2_validate_inode_block() to alongside the existing i_size check to fix it.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-787 · Out-of-bounds write
- Record status
- Modified
Affected
- Linux Kernel < 6.6.136
- Linux Kernel < 6.12.83
- Linux Kernel < 6.18.24
- Linux Kernel < 6.19.14
- Linux Kernel 2.6.24
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43075.md and follow it. Check whether this project is affected by CVE-2026-43075. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0c1af902223b6fcedb60904ca0b551254686c7b9
- https://git.kernel.org/stable/c/69d3c69ade1e4285ab4ca48fe7acee0767e65604
- https://git.kernel.org/stable/c/7bc5da4842bed3252d26e742213741a4d0ac1b14
- https://git.kernel.org/stable/c/947f953978b0d9463498d548d0f054f5a75be2e9
- https://git.kernel.org/stable/c/e2c9dc6b6e96f3585f2a1062ca3374a52db0938f
References
- https://git.kernel.org/stable/c/0c1af902223b6fcedb60904ca0b551254686c7b9
- https://git.kernel.org/stable/c/22df7d4de9c5cd42edf855a1de25f2106088c4c6
- https://git.kernel.org/stable/c/2e6a254f9cedf51b75cc20b8b92e2209bfa04c3e
- https://git.kernel.org/stable/c/68f9cc3bbf2ae501770cea7dc0005fc9a85e48ea
- https://git.kernel.org/stable/c/69d3c69ade1e4285ab4ca48fe7acee0767e65604
- https://git.kernel.org/stable/c/7bc5da4842bed3252d26e742213741a4d0ac1b14
- https://git.kernel.org/stable/c/947f953978b0d9463498d548d0f054f5a75be2e9
- https://git.kernel.org/stable/c/e2c9dc6b6e96f3585f2a1062ca3374a52db0938f