CVE-2026-98553: autofs: fix sbi->pipe file reference leak in autofs_kill_sb()
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 0662b1ff9b383d5a233d344e4dc518c27a17f7b8, 34fa4c1c6e10507dc60e35a82cc9655666946cfd, 3684e2273ba94553af3c5195a46a50214a1a96e3; 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 0662b1ff9b383d5a233d344e4dc518c27a17f7b8, 34fa4c1c6e10507dc60e35a82cc9655666946cfd, 3684e2273ba94553af3c5195a46a50214a1a96e3; 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: autofs: fix sbi->pipe file reference leak in autofs_kill_sb() When autofs_fill_super() fails before clearing AUTOFS_SBI_CATATONIC (for example, when find_get_pid() fails on an invalid pgrp mount option, or when an fs_context is closed before mounting), deactivate_locked_super() invokes autofs_kill_sb() -> autofs_catatonic_mode(sbi). Because AUTOFS_SBI_CATATONIC is still set in sbi->flags, autofs_catatonic_mode() returns early without calling fput(sbi->pipe), permanently leaking the pipe struct file reference. Explicitly release sbi->pipe in autofs_kill_sb() if it is still non-NULL after autofs_catatonic_mode().
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
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.
Is your version affected? Check itNoroxi 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
- 4.18affected
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before 3684e2273ba94553af3c5195a46a50214a1a96e3affected · git
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before 0662b1ff9b383d5a233d344e4dc518c27a17f7b8affected · git
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before 34fa4c1c6e10507dc60e35a82cc9655666946cfdaffected · git
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before a58593b501b7be5ad2bc5181bfa8cd4599be257caffected · git
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before f1c57f5b16bbc3571bd479c290996c4d4e1fb931affected · git
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before 4bcb371019097d0e357f097902587401c509bbc9affected · git
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before fc4fd0281ac80b5a3c5a2330f688f0f9d2a420b6affected · git
- ebc921ca9b92a3cf304d99bd7b7f373ec78c7ed7 and later · before aa5e44b29ffe4eaa08cc2237fd65bc2596bc023eaffected · git
- before 4.18not affected · 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:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-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-98551Oct 18, 2026 · perf/core: Fill branch entries with a single assignment0Monitor
- ← EarlierCVE-2026-98552Oct 18, 2026 · perf/core: Fix a refcount leak in attach_perf_ctx_data()0Monitor
- Later →CVE-2026-98554Oct 18, 2026 · vlan: ensure sufficient headroom in vlan_dev_hard_header()0Monitor
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 | 0662b1ff9b383d5a233d344e4dc518c27a17f7b8 | Vendor (CNA) |
| Linux Linux | 34fa4c1c6e10507dc60e35a82cc9655666946cfd | Vendor (CNA) |
| Linux Linux | 3684e2273ba94553af3c5195a46a50214a1a96e3 | Vendor (CNA) |
| Linux Linux | 4bcb371019097d0e357f097902587401c509bbc9 | Vendor (CNA) |
| Linux Linux | a58593b501b7be5ad2bc5181bfa8cd4599be257c | Vendor (CNA) |
| Linux Linux | aa5e44b29ffe4eaa08cc2237fd65bc2596bc023e | Vendor (CNA) |
| Linux Linux | f1c57f5b16bbc3571bd479c290996c4d4e1fb931 | Vendor (CNA) |
| Linux Linux | fc4fd0281ac80b5a3c5a2330f688f0f9d2a420b6 | 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 | 6.12.113-1~deb12u1 · Debian:12 | 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 12, 2026+25 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-1351 · Oct 19, 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/34fa4c1c6e10507dc60e35a82cc9655666946cfd
- git.kernel.org/stable/c/3684e2273ba94553af3c5195a46a50214a1a96e3
- git.kernel.org/stable/c/4bcb371019097d0e357f097902587401c509bbc9
- git.kernel.org/stable/c/a58593b501b7be5ad2bc5181bfa8cd4599be257c
- git.kernel.org/stable/c/aa5e44b29ffe4eaa08cc2237fd65bc2596bc023e
- git.kernel.org/stable/c/f1c57f5b16bbc3571bd479c290996c4d4e1fb931
- git.kernel.org/stable/c/fc4fd0281ac80b5a3c5a2330f688f0f9d2a420b6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.