CVE-2024-42139: ice: Fix improper extts handling
Noroxi assessment
Priority: Monitor (action score 22/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.32% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 00d3b4f54582d4e4a02cda5886bb336eeab268cc, 1f7f63f7165d1c8eee6424b517054db9f672e48b, 2aa24007bf037194e9c72e7c83b26b2e9e07ab62.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 00d3b4f54582d4e4a02cda5886bb336eeab268cc, 1f7f63f7165d1c8eee6424b517054db9f672e48b, 2aa24007bf037194e9c72e7c83b26b2e9e07ab62 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: ice: Fix improper extts handling Extts events are disabled and enabled by the application ts2phc. However, in case where the driver is removed when the application is running, a specific extts event remains enabled and can cause a kernel crash. As a side effect, when the driver is reloaded and application is started again, remaining extts event for the channel from a previous run will keep firing and the message "extts on unexpected channel" might be printed to the user. To avoid that, extts events shall be disabled when PTP is released.
- Published
- Jul 30, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-754
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 5.14affected
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 2aa24007bf037194e9c72e7c83b26b2e9e07ab62affected · git
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 1f7f63f7165d1c8eee6424b517054db9f672e48baffected · git
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 9f69b31ae9e25dec27ad31fbc64dd99af16ee3d3affected · git
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 00d3b4f54582d4e4a02cda5886bb336eeab268ccaffected · git
- before 5.14not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.9.9 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.14 and later · before 6.9.9
- linux linux kernel6.10
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.192-1 | 6.1.192-1 |
| Debian:13 | linux | before 6.9.9-1 | 6.9.9-1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.85.1.el9_2 | 0:7.0.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-doc | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-284.85.1.el9_2 | 0:5.14.0-284.85.1.el9_2 |
+54
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-42128Jul 30, 2024 · leds: an30259a: Use devm_mutex_init() for mutex initialization22Monitor
- ← EarlierCVE-2024-42131Jul 30, 2024 · mm: avoid overflows in dirty throttling logic17Monitor
- Later →CVE-2024-42154Jul 30, 2024 · tcp_metrics: validate source addr length17Monitor
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 | 00d3b4f54582d4e4a02cda5886bb336eeab268cc | Vendor (CNA) |
| Linux Linux | 1f7f63f7165d1c8eee6424b517054db9f672e48b | Vendor (CNA) |
| Linux Linux | 2aa24007bf037194e9c72e7c83b26b2e9e07ab62 | Vendor (CNA) |
| Linux Linux | 9f69b31ae9e25dec27ad31fbc64dd99af16ee3d3 | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.9.9-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.85.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | 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.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-39682402 days aparttls: fix handling of zero-length records on the rx_listKEV70This week
- CVE-2024-421590 days apartscsi: mpi3mr: Sanitise num_phys31Monitor
- CVE-2024-421600 days apartf2fs: check validation of fault attrs in f2fs_build_fault_attr()31Monitor
- CVE-2024-4228418 days aparttipc: Return non-zero value from tipc_udp_addr2str() on error31Monitor
- CVE-2024-4772783 days apartx86/tdx: Fix "in-kernel MMIO" check31Monitor
- CVE-2021-47014153 days apartnet/sched: act_ct: fix wild memory access when clearing fragments31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1106 · Jul 31, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:L/AC:L/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.