Linux kernel NULL dereference in s390 CTCM XID validation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 293d984f0e3604c04dcdbf00117ddc1e5d4b1909 · < 34fa3607b7604b3052b19cec8b0ad644818cdd2a| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s s390/ctcm XID validation can dereference a NULL pointer when the peer XID is NULL or read/write channel pairing mismatches. The input does not specify an attacker path, authentication requirements, or whether user interaction is needed.
Teams running the Linux kernel with s390/ctcm should check their exposure; affected versions are not specified.