Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-93140: udf: Mark LVID buffer as uptodate before marking it dirty

Noroxi assessment

Priority: Monitor (action score 0/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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 11afe1912140f79d5af3091a54b181ef72fce1a5, 2.6.28, 2.6.33.

Low priority for now. Upgrade to Linux Linux 11afe1912140f79d5af3091a54b181ef72fce1a5, 2.6.28, 2.6.33 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: udf: Mark LVID buffer as uptodate before marking it dirty When an I/O error occurs while writing the Logical Volume Integrity Descriptor (LVID) buffer to the block device, the block layer's completion handler (`end_buffer_write_sync()`) clears the `BH_Uptodate` flag on the buffer. However, the buffer still contains valid LVID data in memory. If the filesystem is subsequently remounted read-write or synced, `udf_open_lvid()` or `udf_sync_fs()` will modify the LVID buffer and call `mark_buffer_dirty()`. This triggers a spurious `WARN_ON_ONCE(!buffer_uptodate(bh))` warning in `mark_buffer_dirty()` because the buffer is not marked uptodate, even though its in-memory contents are valid and are about to be overwritten. To prevent this spurious warning, unconditionally set the `BH_Uptodate` flag before calling `mark_buffer_dirty()` in `udf_open_lvid()` and `udf_sync_fs()`. This acknowledges that the in-memory buffer is valid and matches the workaround previously applied to `udf_close_lvid()` in commit 853a0c25baf9 ("udf: Mark LVID buffer as uptodate before marking it dirty"). Extending this workaround ensures consistent behavior across all LVID updates. Buffer I/O error on dev loop0, logical block 128, lost sync page write ------------[ cut here ]------------ !buffer_uptodate(bh) WARNING: fs/buffer.c:1087 at mark_buffer_dirty+0x299/0x410 fs/buffer.c:1087 ... Call Trace: <TASK> udf_open_lvid+0x369/0x5b0 fs/udf/super.c:2078 udf_reconfigure+0x336/0x540 fs/udf/super.c:679 reconfigure_super+0x232/0x8f0 fs/super.c:1080 vfs_cmd_reconfigure fs/fsopen.c:268 [inline] vfs_fsconfig_locked+0x171/0x320 fs/fsopen.c:297 __do_sys_fsconfig fs/fsopen.c:463 [inline] __se_sys_fsconfig+0x6b9/0x810 fs/fsopen.c:350 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94 </TASK>

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2026-93140

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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

    • c7da4ed95a78e38fdaffb06eaf1a3f3318b1add6, c005218328597211008a4d33a91e2952798e3556, 1357ed0b4b9db30846377febb40a847d6103c991, 43f4a516b2f5492bc597f3753b693ad8adc62748, 3.3affected
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before e6461ef34f91ad7dbffdf912b3d661a7dd892931affected · git
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before 359cea636f4a74a96c01a8050f155e12840c079aaffected · git
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before a4c4e38b356ad4c1f90478124922917489137c08affected · git
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before 8034ddf4751d9143c5ef7eebe3d4f33218fdd378affected · git
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before ee477e5204f764444e60699280abf5936c2a6ae6affected · git
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before 11afe1912140f79d5af3091a54b181ef72fce1a5affected · git
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before c4058355d27488a3cd31c60c032335f77c4fdcfcaffected · git
    • 853a0c25baf96b028de1654bea1e0c8857eadf3d and later · before fb0601134c7e51728bd098abc6909315de1e5d86affected · git
    • 2.6.27.62 and later · before 2.6.28affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93138Sep 17, 2026 · bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux
    31Monitor
  • ← EarlierCVE-2026-93139Sep 17, 2026 · drm/amdgpu/mes: Fix hung_queue_db_array loop limit for multi-XCC
    0Monitor
  • Later →CVE-2026-93141Sep 17, 2026 · usb: gadget: r8a66597: avoid double free of ep0_req in probe error path
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux11afe1912140f79d5af3091a54b181ef72fce1a5Vendor (CNA)
Linux Linux2.6.28Vendor (CNA)
Linux Linux2.6.33Vendor (CNA)
Linux Linux3.1Vendor (CNA)
Linux Linux3.3Vendor (CNA)
Linux Linux359cea636f4a74a96c01a8050f155e12840c079aVendor (CNA)
Linux Linux8034ddf4751d9143c5ef7eebe3d4f33218fdd378Vendor (CNA)
Linux Linuxa4c4e38b356ad4c1f90478124922917489137c08Vendor (CNA)
Linux Linuxc4058355d27488a3cd31c60c032335f77c4fdcfcVendor (CNA)
Linux Linuxe6461ef34f91ad7dbffdf912b3d661a7dd892931Vendor (CNA)
Linux Linuxee477e5204f764444e60699280abf5936c2a6ae6Vendor (CNA)
Linux Linuxfb0601134c7e51728bd098abc6909315de1e5d86Vendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records