NVD / CVE Program· CNA Linux

CVE-2026-43076: ocfs2: validate inline data i_size during inode read

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.13% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 131c0b573e1b467b7d553e9ff38003f1acd8f5f2, 1524af3685b35feac76662cc551cbc37bd14775f, 37f074e65f24f10f8d8df224a572e4cb9e6faf63.

Low priority for now. Upgrade to Linux Linux 131c0b573e1b467b7d553e9ff38003f1acd8f5f2, 1524af3685b35feac76662cc551cbc37bd14775f, 37f074e65f24f10f8d8df224a572e4cb9e6faf63 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: validate inline data i_size during inode read When reading an inode from disk, ocfs2_validate_inode_block() performs various sanity checks but does not validate the size of inline data. If the filesystem is corrupted, an inode's i_size can exceed the actual inline data capacity (id_count). This causes ocfs2_dir_foreach_blk_id() to iterate beyond the inline data buffer, triggering a use-after-free when accessing directory entries from freed memory. In the syzbot report: - i_size was 1099511627576 bytes (~1TB) - Actual inline data capacity (id_count) is typically <256 bytes - A garbage rec_len (54648) caused ctx->pos to jump out of bounds - This triggered a UAF in ocfs2_check_dir_entry() Fix by adding a validation check in ocfs2_validate_inode_block() to ensure inodes with inline data have i_size <= id_count. This catches the corruption early during inode read and prevents all downstream code from operating on invalid data.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: May 6, 2026
Updated: Aug 5, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-416

Report tools

JSON

Action score

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

Is your version affected? Check it

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 help

Affected 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
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before d012c782abcabe68b5b9e71be58a15e9f9d83dc1affected · git
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before bcd46bc261b215b3b12c557a978299eafa02ecddaffected · git
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before 131c0b573e1b467b7d553e9ff38003f1acd8f5f2affected · git
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before 37f074e65f24f10f8d8df224a572e4cb9e6faf63affected · git
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1baffected · git
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before cd2d765aa7157f852999842af32148128c735d39affected · git
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before 77d0295725109d77f5854ef5b58c0d06c08168ccaffected · git
- 23193e513d1cd69411469f028d56fd175d4a6b07 and later · before 1524af3685b35feac76662cc551cbc37bd14775faffected · 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 records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-43073May 5, 2026 · x86-64: rename misleadingly named '__copy_user_nocache()' function
22Monitor
← EarlierCVE-2026-43075May 6, 2026 · ocfs2: fix out-of-bounds write in ocfs2_write_end_inline
31Monitor
Later →CVE-2026-43077May 6, 2026 · crypto: algif_aead - Fix minimum RX size check for decryption
22Monitor

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	131c0b573e1b467b7d553e9ff38003f1acd8f5f2	Vendor (CNA)
Linux Linux	1524af3685b35feac76662cc551cbc37bd14775f	Vendor (CNA)
Linux Linux	37f074e65f24f10f8d8df224a572e4cb9e6faf63	Vendor (CNA)
Linux Linux	77d0295725109d77f5854ef5b58c0d06c08168cc	Vendor (CNA)
Linux Linux	bcd46bc261b215b3b12c557a978299eafa02ecdd	Vendor (CNA)
Linux Linux	c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1b	Vendor (CNA)
Linux Linux	cd2d765aa7157f852999842af32148128c735d39	Vendor (CNA)
Linux Linux	d012c782abcabe68b5b9e71be58a15e9f9d83dc1	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 researchers

Finders, 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.
No account or password is required.
A user must open a link or visit a page.
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: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/131c0b573e1b467b7d553e9ff38003f1acd8f5f2

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records