sysctl: always initialize i_uid/i_gid
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf · < 98ca62ba9e2be5863c7d069f84f7166b45a5b2f4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sysctl: always initialize i_uid/i_gid
Always initialize i_uid/i_gid inside the sysfs core so set_ownership() can safely skip setting them.
Commit 5ec27ec735ba ("fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes.") added defaults for i_uid/i_gid when set_ownership() was not implemented. It also missed adjusting net_ctl_set_ownership() to use the same default values in case the computation of a better value failed.
From the CVE record · Linux
The Linux kernel may leave i_uid/i_gid ownership values improperly initialized for /proc/sys inodes when ownership computation fails. The input does not specify an attacker action, access requirements, or whether user interaction is needed.
Engineers running the Linux kernel should check their installations; affected versions are not specified.