Linux Kernel up to 7.3-rc2 exec do_close_on_exec deadlock

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.00-

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.3-rc2 and classified as critical. This affects the function do_close_on_exec of the component exec. The manipulation results in deadlock. This vulnerability is known as CVE-2026-98388. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.3-rc2. Affected is the function do_close_on_exec of the component exec. The manipulation with an unknown input leads to a deadlock vulnerability. CWE is classifying the issue as CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. This is going to have an impact on availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-98388 since 09/25/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 10/14/2026). This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2.7 or 7.3-rc3 eliminates this vulnerability. Applying the patch 955973fff4a36d39a848b00cac1706863f568fe1/550feab5b01000ab314868b62211fb3ddfd600e8/5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38/3feb4020bfb7ccf0d347f27051639d25e19cd65d/0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53/19ddef61ee0a49782a60f8f497e50597ad5de2da/63be3d8511bdafa095cd14a393cbf3c58dbbb928/e780259b54e618ceb4763fbc21314acf3565e813 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Deadlock
CWE: CWE-833 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.271/5.15.222/6.1.189/6.6.158/6.12.111/6.18.53/7.2.7/7.3-rc3
Patch: 955973fff4a36d39a848b00cac1706863f568fe1/550feab5b01000ab314868b62211fb3ddfd600e8/5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38/3feb4020bfb7ccf0d347f27051639d25e19cd65d/0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53/19ddef61ee0a49782a60f8f497e50597ad5de2da/63be3d8511bdafa095cd14a393cbf3c58dbbb928/e780259b54e618ceb4763fbc21314acf3565e813

Timelineinfo

09/25/2026 CVE reserved
10/14/2026 +19 days Advisory disclosed
10/14/2026 +0 days VulDB entry created
10/14/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-98388 (🔒)
GCVE (CVE): GCVE-0-2026-98388
GCVE (VulDB): GCVE-100-419850

Entryinfo

Created: 10/14/2026 15:58
Changes: 10/14/2026 15:58 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!