LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23165: sfc: fix deadlock in RSS config read

In the Linux kernel, the following vulnerability has been resolved: sfc: fix deadlock in RSS config read Since cited commit, core locks the net_device's rss_lock when handling ethtool -x command, so driver's implementation should not lock it again. Remove the latter.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a deadlock when reading RSS network configuration through the sfc driver. In business terms, affected systems may hang or lose responsiveness in that network management path. The public record does not provide a CVSS score, broad impact statement, or evidence of active exploitation.

Executive priority

Track and patch through normal Linux kernel maintenance unless the affected sfc driver is used on critical network infrastructure. Escalate if vendors classify your distribution package as vulnerable or if operational hangs are observed.

Technical view

The vulnerability is in the Linux kernel sfc driver. The kernel core already holds net_device rss_lock while handling an ethtool RSS configuration read, and the driver attempted to lock it again, causing a deadlock. The referenced stable commits remove the duplicate lock.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the sfc network driver in use. The record lists affected Linux versions including 6.17, 6.18.9, and 6.19, but distribution backport status must be checked separately.

Exploitation context

The source bundle does not cite active exploitation, public weaponization, KEV listing, or remote unauthenticated attack details. It describes a deadlock during RSS configuration reads, so treat this primarily as an availability and operational reliability risk based on current evidence.

Researcher notes

Evidence is narrow: the record identifies a locking bug and two kernel stable commits, but no CVSS, CWE, exploit status, or detailed affected distribution matrix. Validation should focus on kernel provenance, driver presence, and vendor backport mapping.

Mitigation direction

  • Apply kernel updates that include the referenced stable fixes when available from your vendor.
  • Check distribution advisories for backported fixes to your exact kernel package.
  • Prioritize systems using the sfc driver for network connectivity or management.
  • Avoid inventing compensating controls; follow vendor guidance if patches are unavailable.

Validation and detection

  • Inventory Linux kernel versions and identify systems using the sfc driver.
  • Compare installed kernel packages against vendor advisories and stable fix commits.
  • Review whether affected systems expose or rely on ethtool RSS configuration reads operationally.
  • Confirm patched systems no longer map to the affected kernel versions in vendor guidance.
Prepared
Confidence
medium
Sources
4

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-2026-23165 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
0ADP providers
3Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux040cef30b5e67271e3193e0206f82b206fc97095, 040cef30b5e67271e3193e0206f82b206fc97095unaffected
LinuxLinux6.17, 0, 6.18.9, 6.19affected
Weakness

CWE details

No CWE listed

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