CVE-2026-23165
Deadlock Vulnerability in Linux sfc Driver RSS Configuration
Publication date: 2026-02-14
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.17 (inc) to 6.18.9 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves a deadlock issue in the Linux kernel related to the RSS (Receive Side Scaling) configuration read process.
Specifically, the kernel's core locks the network device's rss_lock when handling the ethtool -x command, but the driver implementation was also locking it again, causing a deadlock.
The fix removes the redundant locking in the driver to prevent this deadlock.
How can this vulnerability impact me? :
This deadlock vulnerability can cause the system to hang or become unresponsive when the ethtool -x command is executed, potentially affecting network performance or availability.
Such a deadlock could disrupt normal network operations, leading to denial of service conditions on affected systems.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know