LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46861: usbnet: ipheth: do not stop RX on failing RX callback

In the Linux kernel, the following vulnerability has been resolved: usbnet: ipheth: do not stop RX on failing RX callback RX callbacks can fail for multiple reasons: * Payload too short * Payload formatted incorrecly (e.g. bad NCM framing) * Lack of memory None of these should cause the driver to seize up. Make such failures non-critical and continue processing further incoming URBs.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause the ipheth USB network driver to stop receiving traffic after certain receive errors. The business impact is likely availability disruption on systems using this driver, not confirmed data theft or code execution. Severity is not scored in the provided sources.

Executive priority

Treat as a targeted availability risk rather than a broad emergency based on current evidence. Prioritize patch tracking for Linux endpoints or appliances using USB network tethering, and rely on vendor kernel advisories for confirmed package fixes.

Technical view

The vulnerability is in Linux kernel usbnet ipheth receive handling. Failed RX callbacks from short payloads, malformed NCM framing, or memory allocation failure could make the driver seize up. The kernel fix makes those RX failures non-critical and continues processing later incoming URBs.

Likely exposure

Exposure appears limited to Linux systems using the ipheth USB network driver path. The source lists Linux kernel release entries including 6.5, 6.6.52, 6.10.11, and 6.11 as affected, but distro package mapping is not provided.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The described trigger involves receive callback failures caused by short, malformed, or memory-failure conditions. No exploit maturity, remote reachability, or attacker prerequisites are stated.

Researcher notes

The public description is concise and lacks CVSS, CWE, exploitability, and distro package details. Analysis should focus on kernel version mapping, ipheth driver usage, and whether the stable commits are included in downstream kernels. Avoid assuming broader usbnet impact beyond the stated ipheth path.

Mitigation direction

  • Check your Linux distribution security advisories for CVE-2024-46861 fixes.
  • Upgrade to a kernel package containing the referenced stable fixes.
  • Prioritize systems where ipheth or USB tethering is enabled or operationally important.
  • If updates are unavailable, review vendor guidance for temporary exposure reduction.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Check whether the ipheth driver is present, loaded, or required.
  • Map installed distro kernel packages to vendor advisories for this CVE.
  • Confirm patched kernel builds include the referenced stable commits.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-46861 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa2d274c62e44b1995c170595db3865c6fe701226, a2d274c62e44b1995c170595db3865c6fe701226, a2d274c62e44b1995c170595db3865c6fe701226unaffected
LinuxLinux6.5, 0, 6.6.52, 6.10.11, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.