LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35889: idpf: fix kernel panic on unknown packet types

In the Linux kernel, the following vulnerability has been resolved: idpf: fix kernel panic on unknown packet types In the very rare case where a packet type is unknown to the driver, idpf_rx_process_skb_fields would return early without calling eth_type_trans to set the skb protocol / the network layer handler. This is especially problematic if tcpdump is running when such a packet is received, i.e. it would cause a kernel panic. Instead, call eth_type_trans for every single packet, even when the packet type is unknown.

HighCVSS 8.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A rare network packet condition can crash affected Linux systems using the idpf network driver, particularly while tcpdump is capturing traffic. The primary business risk is service interruption. The supplied CVSS score is 8.6, but the sources do not establish widespread triggering or exploitation.

Executive priority

Prioritize remediation for production systems that use idpf and perform packet capture, especially where an unexpected reboot would disrupt critical services. Other Linux systems should first be screened for actual idpf usage. There is no supplied evidence of active exploitation, so urgency should reflect exposure and availability impact rather than an assumed attack campaign.

Technical view

For an unknown packet type, idpf_rx_process_skb_fields could return before eth_type_trans assigned the skb protocol and network-layer handler. If the packet continued through capture processing, especially with tcpdump running, the missing protocol state could cause a kernel panic. The fix calls eth_type_trans for every packet.

Likely exposure

Exposure is limited to Linux systems running an affected kernel and using the idpf network driver. Risk is elevated where packet capture tools such as tcpdump operate. The bundle identifies versions beginning at 6.7 and references 6.8.5 and 6.9, but its version-range encoding is insufficiently clear for precise inclusion decisions.

Exploitation context

The CVSS vector describes network reachability without privileges or user interaction. However, the source bundle calls the triggering condition very rare, provides no exploit evidence, and marks the CVE absent from KEV. Do not treat active exploitation as established.

Researcher notes

The public description establishes a kernel-panic path caused by incomplete skb initialization for unknown packet types. It does not identify a CWE, demonstrate attacker control of the triggering packet type, or clarify exploit reliability. The affected-version fields are ambiguous; validate distribution backports against the referenced commits instead of relying solely on version numbers.

Mitigation direction

  • Apply a vendor-supported Linux kernel update containing the referenced idpf fix.
  • Confirm the selected kernel includes one of the referenced stable commits or its backport.
  • Prioritize systems using idpf where tcpdump or other packet capture routinely runs.
  • Check Linux distribution security guidance for exact fixed package versions.

Validation and detection

  • Inventory kernel versions and determine which systems load or use the idpf driver.
  • Review vendor changelogs or kernel sources for the referenced fix or an equivalent backport.
  • Identify systems where tcpdump or comparable packet capture runs on idpf interfaces.
  • After updating, confirm systems boot normally and idpf networking and packet capture remain functional.
  • Review kernel logs for prior panics associated with idpf receive processing.
Prepared
Confidence
medium
Sources
4

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-35889 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
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H3.94.7Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2024-35889Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3a8845af66edb340ba9210bb8a0da040c7d6e590, 3a8845af66edb340ba9210bb8a0da040c7d6e590unaffected
LinuxLinux6.7, 0, 6.8.5, 6.9affected
Weakness

CWE details

No CWE listed

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