What is CVE-2023-52596?

CVE-2023-52596 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Out-of-bounds Write flaw (CWE-787), affecting Linux kernel versions from 6.6 onward and patched in 6.6.16, 6.7.4 and 6.8. CVE-2023-52596 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2023-52596?

CVE-2023-52596 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2023-52596?

Yes, CVE-2023-52596 has been patched. Fixed versions include 6.6.16, 6.7.4 and 6.8. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2023-52596 actively exploited?

CVE-2023-52596 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Out-of-bounds Write (CWE-787)?

The product writes data past the end or before the beginning of the intended buffer. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/787.html

CVE-2023-52596

Medium

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.

Package Linux Kernel

Published 2024-03-06

Last modified 2025-02-14

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-787

CVE-2023-52596 is a Out-of-bounds Write vulnerability

What is Out-of-bounds Write?

The product writes data past the end or before the beginning of the intended buffer. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.6 and later are affected. Fixed in 6.6.16, 6.7.4, 6.8 and their respective stable series.

Affected from

≥ 6.6

Fixed in

✓ 6.6.16 6.6.x ✓ 6.7.4 6.7.x ✓ 6.8

References

3 total

Kernel Git
https://git.kernel.org/stable/c/15893975e9e382f8294ea8d926f08dc2d8d39ede

Mailing List Patch
Kernel Git
https://git.kernel.org/stable/c/2ae7081bc10123b187e36a4f3a8e53768de31489

Mailing List Patch
Kernel Git
https://git.kernel.org/stable/c/315552310c7de92baea4e570967066569937a843

Mailing List Patch

Details

CVE ID CVE-2023-52596

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2024-03-06

Modified 2025-02-14

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2023-52596?

CVE-2023-52596 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Out-of-bounds Write flaw (CWE-787) . It affects Linux kernel versions from 6.6 onward and has been patched in 6.6.16, 6.7.4 and 6.8. CVE-2023-52596 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2023-52596?

CVE-2023-52596 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2023-52596?

Yes. CVE-2023-52596 has been patched. Fixed versions include 6.6.16, 6.7.4 and 6.8. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2023-52596 actively exploited?

No. CVE-2023-52596 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.