CVE-2026-43075: ocfs2: fix out-of-bounds write in ocfs2_write_end_inline
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0c1af902223b6fcedb60904ca0b551254686c7b9, 22df7d4de9c5cd42edf855a1de25f2106088c4c6, 2e6a254f9cedf51b75cc20b8b92e2209bfa04c3e.
Low priority for now. Upgrade to Linux Linux 0c1af902223b6fcedb60904ca0b551254686c7b9, 22df7d4de9c5cd42edf855a1de25f2106088c4c6, 2e6a254f9cedf51b75cc20b8b92e2209bfa04c3e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 6, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.24.1 and later · before 6.6.136
- linux linux kernel6.7 and later · before 6.12.83
- linux linux kernel6.13 and later · before 6.18.24
- linux linux kernel6.19 and later · before 6.19.14
- linux linux kernel2.6.24
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.24affected
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before 68f9cc3bbf2ae501770cea7dc0005fc9a85e48eaaffected · git
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before 2e6a254f9cedf51b75cc20b8b92e2209bfa04c3eaffected · git
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before 22df7d4de9c5cd42edf855a1de25f2106088c4c6affected · git
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before e2c9dc6b6e96f3585f2a1062ca3374a52db0938faffected · git
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before 947f953978b0d9463498d548d0f054f5a75be2e9affected · git
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before 0c1af902223b6fcedb60904ca0b551254686c7b9affected · git
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before 69d3c69ade1e4285ab4ca48fe7acee0767e65604affected · git
- 1afc32b952335f665327a1a9001ba1b44bb76fd9 and later · before 7bc5da4842bed3252d26e742213741a4d0ac1b14affected · git
- before 2.6.24not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.14-1 | 6.19.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43071May 5, 2026 · dcache: Limit the minimal number of bucket to two36Monitor
- ← EarlierCVE-2026-43073May 5, 2026 · x86-64: rename misleadingly named '__copy_user_nocache()' function22Monitor
- Later →CVE-2026-43076May 6, 2026 · ocfs2: validate inline data i_size during inode read31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0c1af902223b6fcedb60904ca0b551254686c7b9 | Vendor (CNA) |
| Linux Linux | 22df7d4de9c5cd42edf855a1de25f2106088c4c6 | Vendor (CNA) |
| Linux Linux | 2e6a254f9cedf51b75cc20b8b92e2209bfa04c3e | Vendor (CNA) |
| Linux Linux | 68f9cc3bbf2ae501770cea7dc0005fc9a85e48ea | Vendor (CNA) |
| Linux Linux | 69d3c69ade1e4285ab4ca48fe7acee0767e65604 | Vendor (CNA) |
| Linux Linux | 7bc5da4842bed3252d26e742213741a4d0ac1b14 | Vendor (CNA) |
| Linux Linux | 947f953978b0d9463498d548d0f054f5a75be2e9 | Vendor (CNA) |
| Linux Linux | e2c9dc6b6e96f3585f2a1062ca3374a52db0938f | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/22df7d4de9c5cd42edf855a1de25f2106088c4c6
- git.kernel.org/stable/c/2e6a254f9cedf51b75cc20b8b92e2209bfa04c3e
- git.kernel.org/stable/c/68f9cc3bbf2ae501770cea7dc0005fc9a85e48ea
- git.kernel.org/stable/c/69d3c69ade1e4285ab4ca48fe7acee0767e65604
- git.kernel.org/stable/c/7bc5da4842bed3252d26e742213741a4d0ac1b14
- git.kernel.org/stable/c/947f953978b0d9463498d548d0f054f5a75be2e9
- git.kernel.org/stable/c/e2c9dc6b6e96f3585f2a1062ca3374a52db0938f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.