GHSA-2CQV-6948-3374
Vulnerability from github – Published: 2025-04-16 15:34 – Updated: 2025-04-16 15:34In the Linux kernel, the following vulnerability has been resolved:
exec: fix the racy usage of fs_struct->in_exec
check_unsafe_exec() sets fs->in_exec under cred_guard_mutex, then execve() paths clear fs->in_exec lockless. This is fine if exec succeeds, but if it fails we have the following race:
T1 sets fs->in_exec = 1, fails, drops cred_guard_mutex
T2 sets fs->in_exec = 1
T1 clears fs->in_exec
T2 continues with fs->in_exec == 0
Change fs/exec.c to clear fs->in_exec with cred_guard_mutex held.
{
"affected": [],
"aliases": [
"CVE-2025-22029"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-16T15:15:55Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nexec: fix the racy usage of fs_struct-\u003ein_exec\n\ncheck_unsafe_exec() sets fs-\u003ein_exec under cred_guard_mutex, then execve()\npaths clear fs-\u003ein_exec lockless. This is fine if exec succeeds, but if it\nfails we have the following race:\n\n\tT1 sets fs-\u003ein_exec = 1, fails, drops cred_guard_mutex\n\n\tT2 sets fs-\u003ein_exec = 1\n\n\tT1 clears fs-\u003ein_exec\n\n\tT2 continues with fs-\u003ein_exec == 0\n\nChange fs/exec.c to clear fs-\u003ein_exec with cred_guard_mutex held.",
"id": "GHSA-2cqv-6948-3374",
"modified": "2025-04-16T15:34:39Z",
"published": "2025-04-16T15:34:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22029"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/753a620a7f8e134b444f89fe90873234e894e21a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a6b5070721503fb6021ebed51c925ffc66b1c5ab"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/af7bb0d2ca459f15cb5ca604dab5d9af103643f0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b519f2e5800fe2391b7545ba6889df795828e885"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e2d8e7bd3314485e0b3b08380c659b3d1d67ed6a"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.