CVE-2025-38617
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-22

Last updated on: 2026-03-18

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net/packet: fix a race in packet_set_ring() and packet_notifier() When packet_set_ring() releases po->bind_lock, another thread can run packet_notifier() and process an NETDEV_UP event. This race and the fix are both similar to that of commit 15fe076edea7 ("net/packet: fix a race in packet_bind() and packet_notifier()"). There too the packet_notifier NETDEV_UP event managed to run while a po->bind_lock critical section had to be temporarily released. And the fix was similarly to temporarily set po->num to zero to keep the socket unhooked until the lock is retaken. The po->bind_lock in packet_set_ring and packet_notifier precede the introduction of git history.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-22
Last Modified
2026-03-18
Generated
2026-05-07
AI Q&A
2025-08-22
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel 6.1.153-1
linux linux_kernel 5.10.244-1
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a race condition in the Linux kernel's packet_set_ring() and packet_notifier() functions. Specifically, when packet_set_ring() releases a lock (po->bind_lock), another thread can run packet_notifier() and process a NETDEV_UP event simultaneously. This can cause inconsistent or unexpected behavior because the critical section protected by the lock is temporarily released, allowing concurrent access. The fix involves temporarily setting po->num to zero to keep the socket unhooked until the lock is reacquired, preventing the race.


How can this vulnerability impact me? :

This race condition could lead to unpredictable behavior in network packet handling within the Linux kernel, potentially causing instability or incorrect processing of network events. While the exact impact depends on the system and usage, it may affect network reliability or security by allowing concurrent access to shared resources without proper synchronization.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart