Unknown

CVE-2026-98388 — exec: do_close_on_exec() before taking exec_update_lock

In the Linux kernel, the following vulnerability has been resolved: exec: do_close_on_exec() before taking exec_update_lock do_close_on_exec() currently happens while holding the exec_update_lock, which is used in a lot of places that access process state to synchronize access checks. I recently added another such use of exec_update_lock, causing a regression. do_close_on_exec() can block waiting for a reply from a filesystem. That means a hung filesystem can block codepaths that use exec_update_lock; and it also means that a FUSE filesystem which attempts to inspect the calling process can deadlock. To avoid such problems, move do_close_on_exec() before the exec_update_lock is taken, but after the FD table has been copied if necessary. I have looked through all the calls between the old and new position of the do_close_on_exec() call; there seems to be no file descriptor table access in between.

Published Oct 14, 2026 · Updated Oct 14, 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

No scoring signals.

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

—

No EPSS score.

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 c1cfd63326f5d09999134e9052c353faf738286eversion 7.2≥ 7.1.4 and < 7.2≥ 6.18.40 and < 6.18.53≥ 6.12.97 and < 6.12.111≥ 6.6.145 and < 6.6.158≥ 6.1.178 and < 6.1.189≥ 5.15.212 and < 5.15.222 and 9 more ≥ 5.10.261 and < 5.10.271≥ ae1e630bcaac739f625822078edbaea98366930d and < 955973fff4a36d39a848b00cac1706863f568fe1≥ 6650527444dadc63d84aa939d14ecba4fadb2f69 and < e780259b54e618ceb4763fbc21314acf3565e813≥ 6650527444dadc63d84aa939d14ecba4fadb2f69 and < 63be3d8511bdafa095cd14a393cbf3c58dbbb928≥ f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 and < 19ddef61ee0a49782a60f8f497e50597ad5de2da≥ 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4 and < 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53≥ 7456ae990a9738962b33146916fabca62ae3d4e0 and < 3feb4020bfb7ccf0d347f27051639d25e19cd65d≥ bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9 and < 5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38≥ d54f14655fd7d7b293698a8b6918563c4c0465e7 and < 550feab5b01000ab314868b62211fb3ddfd600e8	Vulnerable	CVE Program (cve.org) e CISA ADP

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 14, 2026
Affected products added · linux/linux
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 14, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 14, 2026 · Alertas do Telegram
CVE published
Oct 14, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 14, 2026 – Oct 14, 2026
1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

8 on the record

git.kernel.org/stable/c/3feb4020bfb7ccf0d347f27051639d25e19cd65d
NIST National Vulnerability Database
git.kernel.org/stable/c/0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53
NIST National Vulnerability Database
git.kernel.org/stable/c/550feab5b01000ab314868b62211fb3ddfd600e8
NIST National Vulnerability Database
git.kernel.org/stable/c/955973fff4a36d39a848b00cac1706863f568fe1
NIST National Vulnerability Database
git.kernel.org/stable/c/19ddef61ee0a49782a60f8f497e50597ad5de2da
NIST National Vulnerability Database
git.kernel.org/stable/c/5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38
NIST National Vulnerability Database
git.kernel.org/stable/c/e780259b54e618ceb4763fbc21314acf3565e813
NIST National Vulnerability Database
git.kernel.org/stable/c/63be3d8511bdafa095cd14a393cbf3c58dbbb928
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 12h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 12h
Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d

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 FIRST EPSS score.
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-98388 is "exec: do_close_on_exec() before taking exec_update_lock", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. 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.