CVE-2026-46118pseries/papr-hvpipe: Fix null ptr deref in papr_hvpipe_dev_create_handle()
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: pseries/papr-hvpipe: Fix null ptr deref in papr_hvpipe_dev_create_handle() commit 6d3789d347a7 ("papr-hvpipe: convert papr_hvpipe_dev_create_handle() to FD_PREPARE()"), changed the create handle to FD_PREPARE(), but it caused kernel null-ptr-deref because after call to retain_and_null_ptr(src_info), src_info is re-used for adding it to the global list. Getting the following kernel panic in papr_hvpipe_dev_create_handle() when trying to add src_info to the list. Kernel attempted to write user page (0) - exploit attempt? (uid: 0) BUG: Kernel NULL pointer dereference on write at 0x00000000 Faulting instruction address: 0xc0000000001b44a0 Oops: Kernel access of bad area, sig: 11 [#1] ... Call Trace: papr_hvpipe_dev_ioctl+0x1f4/0x48c (unreliable) sys_ioctl+0x528/0x1064 system_call_exception+0x128/0x360 system_call_vectored_common+0x15c/0x2ec Now, the error handling with FD_PREPARE's file cleanup and __free(kfree) auto cleanup is getting too convoluted. This is mainly because we need to ensure only 1 user get the srcID handle. To simplify this, we allocate prepare the src_info in the beginning and add it to the global list under a spinlock after checking that no duplicates exist. This simplify the error handling where if the FD_ADD fails, we can simply remove the src_info from the list and consume any pending msg in hvpipe to be cleared, after src_info became visible in the global list.
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Undergoing Analysis
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 09c15bbbed533903e600660ea09098b3b0524f48 before 735439394dde8462f9b50566727fbe333beaadaf; from 6d3789d347a7af5c4b0b2da3af47b8d9da607ab2 before cf51bec1560f8bf115d1476f60335f9d90e110b0; 6d3789d347a7af5c4b0b2da3af47b8d9da607ab2 builds before 1b9f7aafa44f5ce852c00509104d10fd9eb0f402; 51a321dec76f7e39403a0574897a4409a8a700c4; from 6.18.32 before 6.18.33 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.19 before 7.0.7; 6.18.32; 7.1; 7.1 | NVD |
References
- https://git.kernel.org/stable/c/735439394dde8462f9b50566727fbe333beaadafpatch
- https://git.kernel.org/stable/c/cf51bec1560f8bf115d1476f60335f9d90e110b0patch
- https://git.kernel.org/stable/c/1b9f7aafa44f5ce852c00509104d10fd9eb0f402patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.