CVE-2024-38593: net: micrel: Fix receiving the timestamp in the frame for lan8841
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.22% (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 3ddf170e4a604f5d4d9459a36993f5e92b53e8b0, 3fd4282d5f25c3c97fef3ef0b89b82ef4e2bc975, 64a47cf634ae44e92be24ebc982410841093bd7b.
Low priority for now. Upgrade to Linux Linux 3ddf170e4a604f5d4d9459a36993f5e92b53e8b0, 3fd4282d5f25c3c97fef3ef0b89b82ef4e2bc975, 64a47cf634ae44e92be24ebc982410841093bd7b 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: net: micrel: Fix receiving the timestamp in the frame for lan8841 The blamed commit started to use the ptp workqueue to get the second part of the timestamp. And when the port was set down, then this workqueue is stopped. But if the config option NETWORK_PHY_TIMESTAMPING is not enabled, then the ptp_clock is not initialized so then it would crash when it would try to access the delayed work. So then basically by setting up and then down the port, it would crash. The fix consists in checking if the ptp_clock is initialized and only then cancel the delayed work.
- Published
- Jun 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-908
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
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 kernel6.5 and later · before 6.6.33
- linux linux kernel6.7 and later · before 6.8.12
- linux linux kernel6.9 and later · before 6.9.3
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
- 6.5affected
- cc75549548482ed653c23f212544e58cb38ea980 and later · before 3ddf170e4a604f5d4d9459a36993f5e92b53e8b0affected · git
- cc75549548482ed653c23f212544e58cb38ea980 and later · before 3fd4282d5f25c3c97fef3ef0b89b82ef4e2bc975affected · git
- cc75549548482ed653c23f212544e58cb38ea980 and later · before 64a47cf634ae44e92be24ebc982410841093bd7baffected · git
- cc75549548482ed653c23f212544e58cb38ea980 and later · before aea27a92a41dae14843f92c79e9e42d8f570105caffected · git
- before 6.5not affected · semver
- 6.6.33 and later · up to and including 6.6.*not affected · semver
- 6.8.12 and later · up to and including 6.8.*not affected · semver
- 6.9.3 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
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.26.1.el9_4 | 7.3.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.26.1.el9_4 | 5.14.0-427.26.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-38591Jun 19, 2024 · RDMA/hns: Fix deadlock on SRQ async events.22Monitor
- ← EarlierCVE-2024-38592Jun 19, 2024 · drm/mediatek: Init `ddp_comp` with devm_kcalloc()22Monitor
- Later →CVE-2024-38594Jun 19, 2024 · net: stmmac: move the EST lock to struct stmmac_priv22Monitor
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 | 3ddf170e4a604f5d4d9459a36993f5e92b53e8b0 | Vendor (CNA) |
| Linux Linux | 3fd4282d5f25c3c97fef3ef0b89b82ef4e2bc975 | Vendor (CNA) |
| Linux Linux | 64a47cf634ae44e92be24ebc982410841093bd7b | Vendor (CNA) |
| Linux Linux | aea27a92a41dae14843f92c79e9e42d8f570105c | Vendor (CNA) |
| almalinux:bpftool | 7.3.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.26.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.8.12-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:kernel | 0:5.14.0-427.26.1.el9_4 · Rocky Linux:9 | 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.
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.
- CVE-2024-50302153 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2024-47685124 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2024-3689820 days apartgpiolib: cdev: fix uninitialised kfifo31Monitor
- CVE-2021-4755326 days apartsched/scs: Reset task stack state in bringup_cpu()31Monitor
- CVE-2024-2702249 days apartfork: defer linking file vma until vma is fully initialized31Monitor
- CVE-2024-50143141 days apartudf: fix uninit-value use in udf_get_fileshortad31Monitor
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.
- 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-908 · Use of Uninitialized ResourceCVSS 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
- 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.