Answer in brief
CVE-2025-38617 records a Unknown severity vulnerability in net/packet: fix a race in packet_set_ring() and packet_notifier(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38617 records a Unknown severity vulnerability in net/packet: fix a race in packet_set_ring() and packet_notifier(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <18f13f2a83eb81be349a9757ba2141ff1da9ad73 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7da733f117533e9b2ebbd530a22ae4028713955c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ba2257034755ae773722f15f4c3ad1dcdad15ca9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7de07705007c7e34995a5599aaab1d23e762d7ca || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <88caf46db8239e6471413d28aabaa6b8bd552805 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2e8fcfd2b1bc754920108b7f2cd75082c5a18df || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e50ccfaca9e3c671cae917dcb994831a859cf588 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1791fd7b845bea0ce9674fcf2febee7bc87a893 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <01d3c8417b9c1b884a8a981a3b886da556512f36 | 18f13f2a83eb81be349a9757ba2141ff1da9ad73, 7da733f117533e9b2ebbd530a22ae4028713955c, ba2257034755ae773722f15f4c3ad1dcdad15ca9, 7de07705007c7e34995a5599aaab1d23e762d7ca, 88caf46db8239e6471413d28aabaa6b8bd552805, f2e8fcfd2b1bc754920108b7f2cd75082c5a18df, e50ccfaca9e3c671cae917dcb994831a859cf588, f1791fd7b845bea0ce9674fcf2febee7bc87a893, 01d3c8417b9c1b884a8a981a3b886da556512f36 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <18f13f2a83eb81be349a9757ba2141ff1da9ad73 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7da733f117533e9b2ebbd530a22ae4028713955c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ba2257034755ae773722f15f4c3ad1dcdad15ca9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7de07705007c7e34995a5599aaab1d23e762d7ca || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <88caf46db8239e6471413d28aabaa6b8bd552805 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2e8fcfd2b1bc754920108b7f2cd75082c5a18df || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e50ccfaca9e3c671cae917dcb994831a859cf588 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1791fd7b845bea0ce9674fcf2febee7bc87a893 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <01d3c8417b9c1b884a8a981a3b886da556512f36 | 18f13f2a83eb81be349a9757ba2141ff1da9ad73, 7da733f117533e9b2ebbd530a22ae4028713955c, ba2257034755ae773722f15f4c3ad1dcdad15ca9, 7de07705007c7e34995a5599aaab1d23e762d7ca, 88caf46db8239e6471413d28aabaa6b8bd552805, f2e8fcfd2b1bc754920108b7f2cd75082c5a18df, e50ccfaca9e3c671cae917dcb994831a859cf588, f1791fd7b845bea0ce9674fcf2febee7bc87a893, 01d3c8417b9c1b884a8a981a3b886da556512f36 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.