CVE-2026-68144

CRITICALCVSS 9.8/10EPSS 0.48%

Last modified

CVE-2026-68144 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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.. EPSS estimates a 0.48% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.48%

39.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 9641458d3ec42def729fde64669abf07f3220cd5, < c4a52cb4da8d57d060b1d52085d25147a238dac2; >= 9641458d3ec42def729fde64669abf07f3220cd5, < df198743859fefba2f824115f8151dd62d7ad6d8; >= 9641458d3ec42def729fde64669abf07f3220cd5, < 1d81e19fc57a5ee55b4497d01bc0510d76fb9578; >= 9641458d3ec42def729fde64669abf07f3220cd5, < 8d931a75a38b9bb584a4071f5ebbd52755fc35ee; >= 9641458d3ec42def729fde64669abf07f3220cd5, < 17f78c0c0d41d738ee236eb6e841e39395188054; >= 9641458d3ec42def729fde64669abf07f3220cd5, < a48a889b60f73edb0399a8b08284a2ab0bd0295f; >= 9641458d3ec42def729fde64669abf07f3220cd5, < 25e3641beb51333bfbb155af2fd2573a61113af2; >= 9641458d3ec42def729fde64669abf07f3220cd5, < 0f71f852a96af9685858ce59fda34ecbf85c283d
LinuxLinux2.6.28

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68144?
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.
How severe is CVE-2026-68144?
CVE-2026-68144 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 0.48% probability of exploitation in the next 30 days.
How do I fix CVE-2026-68144?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-68144?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST