Security readout for executives and security teams
Plain-English summary
A Linux pds_core network driver fault can deadlock during PCI recovery when firmware becomes unresponsive. Driver removal in the same firmware state can also improperly queue reset work. Affected systems may hang or lose reliable device operation. The supplied rating is high, although the public description does not establish how confidentiality or integrity compromise would occur.
Executive priority
Treat as a high-priority reliability and security update for systems actively using pds_core, especially critical network infrastructure. Systems without that driver or associated hardware are less likely to be exposed. Patch through normal vendor channels after confirming applicability; there is no supplied evidence requiring emergency incident response for active exploitation.
Technical view
When firmware status becomes 0xff, the health thread calls pci_reset_function(). Reset preparation then stops and flushes that same thread, causing a self-deadlock. The correction moves PCI reset handling onto the driver's work queue. It also suppresses a device-command reset during teardown when firmware is not running, preventing invalid workqueue activity.
Likely exposure
Exposure requires an affected Linux kernel and use of the pds_core PCI driver. The supplied record identifies the affected line as beginning with Linux 6.7 and includes 6.8.7 and 6.9 boundary information, but its compact version data is ambiguous. Confirm exact vulnerable ranges against the linked stable commits or distribution advisories.
Exploitation context
The CVSS vector describes local access with low privileges, no user interaction, and high potential confidentiality, integrity, and availability impact. However, the supplied sources provide no exploit method or evidence of exploitation in the wild, and the CVE is not listed as KEV. The documented trigger involves failed firmware and driver reset or removal paths.
Researcher notes
The disclosed failure is a re-entrant thread shutdown deadlock plus unsafe reset work during teardown when firmware is down. The fixes separate reset execution from the health thread and gate reset commands on firmware state. The 7.8 CVSS claims high CIA impact, but the supplied narrative chiefly substantiates availability effects; no exploitation primitive or data-impact mechanism is described.
Mitigation direction
- Install a vendor-supported kernel containing the linked stable fixes.
- Prioritize systems that load pds_core and rely on its attached PCI hardware.
- Consult distribution or appliance advisories for exact fixed package versions.
- Avoid unsupported kernel downgrades or improvised driver changes.
Validation and detection
- Record the running kernel and installed vendor package versions.
- Check whether pds_core is present, loaded, or bound to PCI hardware.
- Compare kernel sources or package changelogs with both linked fixes.
- Review logs for firmware-down events, reset hangs, or workqueue warnings.
- Retest device recovery and driver removal after the approved update.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-35968 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/38407914d48273d7f8ab765b9243658afe1c3ab6CVE reference, Linux
- https://git.kernel.org/stable/c/81665adf25d28a00a986533f1d3a5df76b79cad9CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.