CVE-2024-38580: epoll: be better about file lifetimes
Noroxi assessment
Priority: Monitor (action score 18/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.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 16e3182f6322575eb7c12e728ad3c7986a189d5d, 4efaa5acf0a1d2b5947f98abb3acf8bfd966422b, 4f65f4defe4e23659275ce5153541cd4f76ce2d2.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.
Low priority for now. Upgrade to Linux Linux 16e3182f6322575eb7c12e728ad3c7986a189d5d, 4efaa5acf0a1d2b5947f98abb3acf8bfd966422b, 4f65f4defe4e23659275ce5153541cd4f76ce2d2 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: epoll: be better about file lifetimes epoll can call out to vfs_poll() with a file pointer that may race with the last 'fput()'. That would make f_count go down to zero, and while the ep->mtx locking means that the resulting file pointer tear-down will be blocked until the poll returns, it means that f_count is already dead, and any use of it won't actually get a reference to the file any more: it's dead regardless. Make sure we have a valid ref on the file pointer before we call down to vfs_poll() from the epoll routines.
- Published
- Jun 19, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 7.8
- 3.1 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.15.161
- linux linux kernel5.16 and later · before 6.1.93
- linux linux kernel6.2 and later · before 6.6.33
- linux linux kernel6.7 and later · before 6.8.12
- linux linux kernel6.9
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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before cbfd1088e24ec4c1199756a37cb8e4cd0a4b016eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 559214eb4e5c3d05e69428af2fae2691ba1eb784affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4f65f4defe4e23659275ce5153541cd4f76ce2d2affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 16e3182f6322575eb7c12e728ad3c7986a189d5daffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4efaa5acf0a1d2b5947f98abb3acf8bfd966422baffected · git
- before 2.6.12not affected · semver
- 5.15.161 and later · up to and including 5.15.*not affected · semver
- 6.1.93 and later · up to and including 6.1.*not affected · semver
- 6.6.33 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.3.0-427.28.1.el9_4 | 7.3.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.28.1.el9_4 | 5.14.0-427.28.1.el9_4 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-38576Jun 19, 2024 · rcu: Fix buffer overflow in print_cpu_stall_info()28Monitor
- ← EarlierCVE-2024-38577Jun 19, 2024 · rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow31Monitor
- Later →CVE-2024-38581Jun 19, 2024 · drm/amdgpu/mes: fix use-after-free issue31Monitor
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 | 16e3182f6322575eb7c12e728ad3c7986a189d5d | Vendor (CNA) |
| Linux Linux | 4efaa5acf0a1d2b5947f98abb3acf8bfd966422b | Vendor (CNA) |
| Linux Linux | 4f65f4defe4e23659275ce5153541cd4f76ce2d2 | Vendor (CNA) |
| Linux Linux | 559214eb4e5c3d05e69428af2fae2691ba1eb784 | Vendor (CNA) |
| Linux Linux | cbfd1088e24ec4c1199756a37cb8e4cd0a4b016e | Vendor (CNA) |
| almalinux:bpftool | 7.3.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.28.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.94-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+1
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.
No dated events beyond publication.
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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.