Unknown

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

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>

Published Sep 17, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.22%

ahead of 11% of scored CVEs · Oct 16, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	version c7da4ed95a78e38fdaffb06eaf1a3f3318b1add6version 3.3≥ 3.2.6 and < 3.3≥ 3.0.21 and < 3.1≥ 2.6.32.57 and < 2.6.33≥ 2.6.27.62 and < 2.6.28version 43f4a516b2f5492bc597f3753b693ad8adc62748version 1357ed0b4b9db30846377febb40a847d6103c991 and 9 more version c005218328597211008a4d33a91e2952798e3556≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < e6461ef34f91ad7dbffdf912b3d661a7dd892931≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < fb0601134c7e51728bd098abc6909315de1e5d86≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < c4058355d27488a3cd31c60c032335f77c4fdcfc≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < 11afe1912140f79d5af3091a54b181ef72fce1a5≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < ee477e5204f764444e60699280abf5936c2a6ae6≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < 8034ddf4751d9143c5ef7eebe3d4f33218fdd378≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < a4c4e38b356ad4c1f90478124922917489137c08≥ 853a0c25baf96b028de1654bea1e0c8857eadf3d and < 359cea636f4a74a96c01a8050f155e12840c079a	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.22%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 17, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/c4058355d27488a3cd31c60c032335f77c4fdcfc
NIST National Vulnerability Database
git.kernel.org/stable/c/e6461ef34f91ad7dbffdf912b3d661a7dd892931
NIST National Vulnerability Database
git.kernel.org/stable/c/ee477e5204f764444e60699280abf5936c2a6ae6
NIST National Vulnerability Database
git.kernel.org/stable/c/fb0601134c7e51728bd098abc6909315de1e5d86
NIST National Vulnerability Database
git.kernel.org/stable/c/11afe1912140f79d5af3091a54b181ef72fce1a5
NIST National Vulnerability Database
git.kernel.org/stable/c/359cea636f4a74a96c01a8050f155e12840c079a
NIST National Vulnerability Database
git.kernel.org/stable/c/a4c4e38b356ad4c1f90478124922917489137c08
NIST National Vulnerability Database
git.kernel.org/stable/c/8034ddf4751d9143c5ef7eebe3d4f33218fdd378
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 2d
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 2d
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 3d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-93140 is "udf: Mark LVID buffer as uptodate before marking it dirty", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.