Answer in brief
CVE-2026-68144 records a Unknown severity vulnerability in phonet: pep: fix use-after-free in pep_get_sb(). 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 | >=9641458d3ec42def729fde64669abf07f3220cd5 <8d931a75a38b9bb584a4071f5ebbd52755fc35ee || >=9641458d3ec42def729fde64669abf07f3220cd5 <17f78c0c0d41d738ee236eb6e841e39395188054 || >=9641458d3ec42def729fde64669abf07f3220cd5 <a48a889b60f73edb0399a8b08284a2ab0bd0295f || >=9641458d3ec42def729fde64669abf07f3220cd5 <25e3641beb51333bfbb155af2fd2573a61113af2 || >=9641458d3ec42def729fde64669abf07f3220cd5 <0f71f852a96af9685858ce59fda34ecbf85c283d | 8d931a75a38b9bb584a4071f5ebbd52755fc35ee, 17f78c0c0d41d738ee236eb6e841e39395188054, a48a889b60f73edb0399a8b08284a2ab0bd0295f, 25e3641beb51333bfbb155af2fd2573a61113af2, 0f71f852a96af9685858ce59fda34ecbf85c283d |
| Linux/Linuxgeneric | 2.6.28 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
In the Linux kernel, the following vulnerability has been resolved: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68144 records a Unknown severity vulnerability in phonet: pep: fix use-after-free in pep_get_sb(). 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 | >=9641458d3ec42def729fde64669abf07f3220cd5 <8d931a75a38b9bb584a4071f5ebbd52755fc35ee || >=9641458d3ec42def729fde64669abf07f3220cd5 <17f78c0c0d41d738ee236eb6e841e39395188054 || >=9641458d3ec42def729fde64669abf07f3220cd5 <a48a889b60f73edb0399a8b08284a2ab0bd0295f || >=9641458d3ec42def729fde64669abf07f3220cd5 <25e3641beb51333bfbb155af2fd2573a61113af2 || >=9641458d3ec42def729fde64669abf07f3220cd5 <0f71f852a96af9685858ce59fda34ecbf85c283d | 8d931a75a38b9bb584a4071f5ebbd52755fc35ee, 17f78c0c0d41d738ee236eb6e841e39395188054, a48a889b60f73edb0399a8b08284a2ab0bd0295f, 25e3641beb51333bfbb155af2fd2573a61113af2, 0f71f852a96af9685858ce59fda34ecbf85c283d |
| Linux/Linuxgeneric | 2.6.28 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
In the Linux kernel, the following vulnerability has been resolved: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.
Quoted source text, attributed separately from HOL analysis.