CVE-2026-99126unknown
s390/ctcm: Prevent XID null dereference
Impact
In the Linux kernel, the following vulnerability has been resolved:
Source excerpt · LinuxAffected packages
This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Linux · Linux
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 293d984f0e3604c04dcdbf00117ddc1e5d4b1909 to before 34fa3607b7604b3052b19cec8b0ad644818cdd2a | affected |
| 293d984f0e3604c04dcdbf00117ddc1e5d4b1909 to before 8a2f7a4ad1d81612fa65bfa4d392ba1bb2f5eeab | affected |
| 293d984f0e3604c04dcdbf00117ddc1e5d4b1909 to before b264d8422779d69febce914efc47a92a85cc382c | affected |
Linux · Linux
Other versions: affected
| Version / range | Source status |
|---|---|
| 2.6.26 | affected |
| 0 to before 2.6.26 | unaffected |
| 6.18.59 through 6.18.* (inclusive) | unaffected |
| 7.2.13 through 7.2.* (inclusive) | unaffected |
| 7.3 through * (inclusive) | unaffected |
Original source description
In the Linux kernel, the following vulnerability has been resolved:
s390/ctcm: Prevent XID null dereference
The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40 to signal XID validation error. If peer XID is NULL or r/w channel pairing mismatch happens, grp->saved_xid2 is never initialized. An attempt to set the flag in such case leads to NULL dereference.
Fix this by using the always available priv->xid->xid2_flag2 instead of grp->saved_xid2->xid2_flag2 for validation errors.