Review reviewHigh

CVE-2021-47458

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ocfs2: mount fails with buffer overflow in strlen Starting with kernel 5.11 built with CONFIG_FORTIFY_SOURCE mouting an ocfs2 filesystem with either o2cb or pcmk cluster stack fails with the trace below. Problem seems to be that strings for cluster stack and cluster name are not guaranteed to be null terminated in the disk representation, while strlcpy assumes that the source string is always null terminated. This causes a read outside of the source string triggering the buffer overflow detection. detected buffer overflow i...

CVSS
7.8
EPSS
0.25%
15.9% percentile
CISA KEV
Not listed
Published
2024.05.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.25%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ocfs2: mount fails with buffer overflow in strlen Starting with kernel 5.11 built with CONFIG_FORTIFY_SOURCE mouting an ocfs2 filesystem with either o2cb or pcmk cluster stack fails with the trace below. Problem seems to be that strings for cluster stack and cluster name are not guaranteed to be null terminated in the disk representation, while strlcpy assumes that the source string is always null terminated. This causes a read outside of the source string triggering the buffer overflow detection. detected buffer overflow i...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= c74a3bdd9b529d924d1abf986079b783dd105ace < ac011cb3ff7a76b3e0e6e77158ee4ba2f929e1fb, >= c74a3bdd9b529d924d1abf986079b783dd105ace < 4b74ddcc22ee6455946e80a9c4808801f8f8561e, >= c74a3bdd9b529d924d1abf986079b783dd105ace < 232ed9752510de4436468b653d145565669c8498, >= c74a3bdd9b529d924d1abf986079b783dd105ace < 7623b1035ca2d17bde0f6a086ad6844a34648df1, >= c74a3bdd9b529d924d1abf986079b783dd105ace < d3a83576378b4c904f711598dde2c5e881c4295c, >= c74a3bdd9b529d924d1abf986079b783dd105ace < 93be0eeea14cf39235e585c8f56df3b3859deaad, >= c74a3bdd9b529d924d1abf986079b783dd105ace < 0e677ea5b7396f715a76b6b0ef441430e4c4b57f, >= c74a3bdd9b529d924d1abf986079b783dd105ace < b15fa9224e6e1239414525d8d556d824701849fc, >= 3.14, < 4.4.290, >= 4.5 < 4.9.288, >= 4.10 < 4.14.253, >= 4.15 < 4.19.214, >= 4.20 < 5.4.156, >= 5.5 < 5.10.76, >= 5.11 < 5.14.15, 5.15
Fixed versions
4.4.290, 4.9.288, 4.14.253, 4.19.214, 5.4.156, 5.10.76, 5.14.15

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel 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:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787