Review reviewHigh

CVE-2024-38612

Linux Linux, linux_kernel, acrn

In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.

CVSS
7
EPSS
0.68%
48.9% percentile
CISA KEV
Not listed
Published
2024.06.19
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.68%
Technical severityCVSS 7

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.

Affected product and versions

Product
Linux Linux, linux_kernel, acrn
Affected versions
>= 46738b1317e169b281ad74690276916e24d1be6d < 10610575a3ac2a702bf5c57aa931beaf847949c7, >= 46738b1317e169b281ad74690276916e24d1be6d < 646cd236c55e2cb5f146fc41bbe4034c4af5b2a4, >= 46738b1317e169b281ad74690276916e24d1be6d < 00e6335329f23ac6cf3105931691674e28bc598c, >= 46738b1317e169b281ad74690276916e24d1be6d < 1a63730fb315bb1bab97edd69ff58ad45e04bb01, >= 46738b1317e169b281ad74690276916e24d1be6d < e77a3ec7ada84543e75722a1283785a6544de925, >= 46738b1317e169b281ad74690276916e24d1be6d < 3398a40dccb88d3a7eef378247a023a78472db66, >= 46738b1317e169b281ad74690276916e24d1be6d < 85a70ff1e572160f1eeb096ed48d09a1c9d4d89a, >= 46738b1317e169b281ad74690276916e24d1be6d < c04d6a914e890ccea4a9d11233009a2ee7978bf4, >= 46738b1317e169b281ad74690276916e24d1be6d < 160e9d2752181fcf18c662e74022d77d3164cd45, >= 4.10, >= 46738b1317e1 < 0610575a3ac, >= 46738b1317e1 < 646cd236c55e, >= 46738b1317e1 < 00e6335329f2, >= 46738b1317e1 < 1a63730fb315, >= 46738b1317e1 < e77a3ec7ada8, >= 46738b1317e1 < 3398a40dccb8, >= 46738b1317e1 < 85a70ff1e572, >= 46738b1317e1 < c04d6a914e89, >= 46738b1317e1 < 160e9d275218, < V3.1
Fixed versions
4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux_kernel, acrn and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416, CWE-476