CVE-2026-98388: exec: do_close_on_exec() before taking exec_update_lock
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 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53, 19ddef61ee0a49782a60f8f497e50597ad5de2da, 3feb4020bfb7ccf0d347f27051639d25e19cd65d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53, 19ddef61ee0a49782a60f8f497e50597ad5de2da, 3feb4020bfb7ccf0d347f27051639d25e19cd65d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 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: 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 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
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.
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.
—
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
- c1cfd63326f5d09999134e9052c353faf738286e, 7.2affected
- ae1e630bcaac739f625822078edbaea98366930d and later · before 955973fff4a36d39a848b00cac1706863f568fe1affected · git
- d54f14655fd7d7b293698a8b6918563c4c0465e7 and later · before 550feab5b01000ab314868b62211fb3ddfd600e8affected · git
- bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9 and later · before 5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38affected · git
- 7456ae990a9738962b33146916fabca62ae3d4e0 and later · before 3feb4020bfb7ccf0d347f27051639d25e19cd65daffected · git
- 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4 and later · before 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53affected · git
- f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 and later · before 19ddef61ee0a49782a60f8f497e50597ad5de2daaffected · git
- 6650527444dadc63d84aa939d14ecba4fadb2f69 and later · before 63be3d8511bdafa095cd14a393cbf3c58dbbb928affected · git
- 6650527444dadc63d84aa939d14ecba4fadb2f69 and later · before e780259b54e618ceb4763fbc21314acf3565e813affected · git
- 5.10.261 and later · before 5.10.271affected · 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.190-1 | 6.1.190-1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.11-1.1 | 7.2.11-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98386Oct 14, 2026 · scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot0Monitor
- ← EarlierCVE-2026-98387Oct 14, 2026 · s390/crypto: Fix skcipher_walk return code handling in aes_s3900Monitor
- Later →CVE-2026-98389Oct 14, 2026 · drm/amdgpu: skip gfx switch_power_profile during GPU reset0Monitor
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 | 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53 | Vendor (CNA) |
| Linux Linux | 19ddef61ee0a49782a60f8f497e50597ad5de2da | Vendor (CNA) |
| Linux Linux | 3feb4020bfb7ccf0d347f27051639d25e19cd65d | Vendor (CNA) |
| Linux Linux | 5.10.271 | Vendor (CNA) |
| Linux Linux | 5.15.222 | Vendor (CNA) |
| Linux Linux | 550feab5b01000ab314868b62211fb3ddfd600e8 | Vendor (CNA) |
| Linux Linux | 5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38 | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 6.12.111 | Vendor (CNA) |
| Linux Linux | 6.18.53 | Vendor (CNA) |
| Linux Linux | 6.6.158 | Vendor (CNA) |
| Linux Linux | 63be3d8511bdafa095cd14a393cbf3c58dbbb928 | Vendor (CNA) |
| Linux Linux | 7.2 | Vendor (CNA) |
| Linux Linux | 955973fff4a36d39a848b00cac1706863f568fe1 | Vendor (CNA) |
| Linux Linux | e780259b54e618ceb4763fbc21314acf3565e813 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.11-1.1 · openSUSE:Tumbleweed | 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.
- Published
- Fix recordedsame day
- TodayNov 3, 2026+20 d
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 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1334 · Oct 15, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/19ddef61ee0a49782a60f8f497e50597ad5de2da
- git.kernel.org/stable/c/3feb4020bfb7ccf0d347f27051639d25e19cd65d
- git.kernel.org/stable/c/550feab5b01000ab314868b62211fb3ddfd600e8
- git.kernel.org/stable/c/5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38
- git.kernel.org/stable/c/63be3d8511bdafa095cd14a393cbf3c58dbbb928
- git.kernel.org/stable/c/955973fff4a36d39a848b00cac1706863f568fe1
- git.kernel.org/stable/c/e780259b54e618ceb4763fbc21314acf3565e813
Vendor advisories and official records. Exploit/PoC links are deliberately left out.