Bug 1221047 (CVE-2023-52596) - VUL-0: CVE-2023-52596: kernel: sysctl: Fix out of bounds access for empty sysctl registers
Summary: VUL-0: CVE-2023-52596: kernel: sysctl: Fix out of bounds access for empty sys...
Status: RESOLVED FIXED
Alias: CVE-2023-52596
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/396453/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-06 10:09 UTC by SMASH SMASH
Modified: 2024-06-10 12:55 UTC (History)
4 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-03-06 10:09:36 UTC
In the Linux kernel, the following vulnerability has been resolved:

sysctl: Fix out of bounds access for empty sysctl registers

When registering tables to the sysctl subsystem there is a check to see
if header is a permanently empty directory (used for mounts). This check
evaluates the first element of the ctl_table. This results in an out of
bounds evaluation when registering empty directories.

The function register_sysctl_mount_point now passes a ctl_table of size
1 instead of size 0. It now relies solely on the type to identify
a permanently empty register.

Make sure that the ctl_table has at least one element before testing for
permanent emptiness.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52596
https://www.cve.org/CVERecord?id=CVE-2023-52596
https://git.kernel.org/stable/c/15893975e9e382f8294ea8d926f08dc2d8d39ede
https://git.kernel.org/stable/c/2ae7081bc10123b187e36a4f3a8e53768de31489
https://git.kernel.org/stable/c/315552310c7de92baea4e570967066569937a843
Comment 1 Gabriele Sonnu 2024-03-06 15:56:29 UTC
Affected code only present in stable, that already has the fix (2ae7081bc101).
Comment 9 Gabriele Sonnu 2024-06-10 12:55:42 UTC
All done, closing.