Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-46679: ethtool: check device is present when getting link settings

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.24% (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 1d6d9b5b1b95bfeccb84386a51b7e6c510ec13b2, 7a8d98b6d6484d3ad358510366022da080c37cbc, 842a40c7273ba1c1cb30dda50405b328de1d860e.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1d6d9b5b1b95bfeccb84386a51b7e6c510ec13b2, 7a8d98b6d6484d3ad358510366022da080c37cbc, 842a40c7273ba1c1cb30dda50405b328de1d860e 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: ethtool: check device is present when getting link settings A sysfs reader can race with a device reset or removal, attempting to read device state when the device is not actually present. eg: [exception RIP: qed_get_current_link+17] #8 [ffffb9e4f2907c48] qede_get_link_ksettings at ffffffffc07a994a [qede] #9 [ffffb9e4f2907cd8] __rh_call_get_link_ksettings at ffffffff992b01a3 #10 [ffffb9e4f2907d38] __ethtool_get_link_ksettings at ffffffff992b04e4 #11 [ffffb9e4f2907d90] duplex_show at ffffffff99260300 #12 [ffffb9e4f2907e38] dev_attr_show at ffffffff9905a01c #13 [ffffb9e4f2907e50] sysfs_kf_seq_show at ffffffff98e0145b #14 [ffffb9e4f2907e68] seq_read at ffffffff98d902e3 #15 [ffffb9e4f2907ec8] vfs_read at ffffffff98d657d1 #16 [ffffb9e4f2907f00] ksys_read at ffffffff98d65c3f #17 [ffffb9e4f2907f38] do_syscall_64 at ffffffff98a052fb crash> struct net_device.state ffff9a9d21336000 state = 5, state 5 is __LINK_STATE_START (0b1) and __LINK_STATE_NOCARRIER (0b100). The device is not present, note lack of __LINK_STATE_PRESENT (0b10). This is the same sort of panic as observed in commit 4224cfd7fb65 ("net-sysfs: add check for netdevice being present to speed_show"). There are many other callers of __ethtool_get_link_ksettings() which don't have a device presence check. Move this check into ethtool to protect all callers.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Sep 13, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

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.

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-46679

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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 kernel2.6.33 and later · before 5.4.283
  • linux linux kernel5.5 and later · before 5.10.225
  • linux linux kernel5.11 and later · before 5.15.166
  • linux linux kernel5.16 and later · before 6.1.108
  • linux linux kernel6.2 and later · before 6.6.49
  • linux linux kernel6.7 and later · before 6.10.8
  • linux linux kernel6.11

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.33affected
    • d519e17e2d01a0ee9abe083019532061b4438065 and later · before ec7b4f7f644018ac293cb1b02528a40a32917e62affected · git
    • d519e17e2d01a0ee9abe083019532061b4438065 and later · before 842a40c7273ba1c1cb30dda50405b328de1d860eaffected · git
    • d519e17e2d01a0ee9abe083019532061b4438065 and later · before 7a8d98b6d6484d3ad358510366022da080c37cbcaffected · git
    • d519e17e2d01a0ee9abe083019532061b4438065 and later · before 9bba5955eed160102114d4cc00c3d399be9bdae4affected · git
    • d519e17e2d01a0ee9abe083019532061b4438065 and later · before 94ab317024ba373d37340893d1c0358638935fbbaffected · git
    • d519e17e2d01a0ee9abe083019532061b4438065 and later · before 1d6d9b5b1b95bfeccb84386a51b7e6c510ec13b2affected · git
    • d519e17e2d01a0ee9abe083019532061b4438065 and later · before a699781c79ecf6cfe67fb00a0331b4088c7c8466affected · git
    • before 2.6.33not affected · semver
    • 5.4.283 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.112-16.1.112-1
Debian:13linuxbefore 6.10.9-16.10.9-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:7.4.0-503.15.1.el9_50:7.4.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-rt-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-503.15.1.el9_50:5.14.0-503.15.1.el9_5

+96

Same product

linux: all records

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-46711Sep 13, 2024 · mptcp: pm: fix ID 0 endp usage after multiple re-creations
    18Monitor
  • ← EarlierCVE-2024-46712Sep 13, 2024 · drm/vmwgfx: Disable coherent dumb buffers without 3d
    22Monitor
  • Later →CVE-2024-46681Sep 13, 2024 · pktgen: use cpus_read_lock() in pg_net_init()
    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 Linux1d6d9b5b1b95bfeccb84386a51b7e6c510ec13b2Vendor (CNA)
Linux Linux7a8d98b6d6484d3ad358510366022da080c37cbcVendor (CNA)
Linux Linux842a40c7273ba1c1cb30dda50405b328de1d860eVendor (CNA)
Linux Linux94ab317024ba373d37340893d1c0358638935fbbVendor (CNA)
Linux Linux9bba5955eed160102114d4cc00c3d399be9bdae4Vendor (CNA)
Linux Linuxa699781c79ecf6cfe67fb00a0331b4088c7c8466Vendor (CNA)
Linux Linuxec7b4f7f644018ac293cb1b02528a40a32917e62Vendor (CNA)
debian:linux6.1.112-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.4.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-503.15.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage 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.

Credits

All researchers

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.

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.

All national notices →

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (11 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records