Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 19, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

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.

Follow CVE-2024-38593

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.26.1.el9_47.3.0-427.26.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

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_priv
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3ddf170e4a604f5d4d9459a36993f5e92b53e8b0Vendor (CNA)
Linux Linux3fd4282d5f25c3c97fef3ef0b89b82ef4e2bc975Vendor (CNA)
Linux Linux64a47cf634ae44e92be24ebc982410841093bd7bVendor (CNA)
Linux Linuxaea27a92a41dae14843f92c79e9e42d8f570105cVendor (CNA)
almalinux:bpftool7.3.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.8.12-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-427.26.1.el9_4 · Rocky Linux:9Package 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.

EPSS, last 120 days

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.

Finders, 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 bufferKEV
    52Plan
  • CVE-2024-47685124 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
    36Monitor
  • CVE-2024-3689820 days apartgpiolib: cdev: fix uninitialised kfifo
    31Monitor
  • 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 initialized
    31Monitor
  • CVE-2024-50143141 days apartudf: fix uninit-value use in udf_get_fileshortad
    31Monitor

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

CVSS 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

All records