Review reviewHigh

CVE-2024-26763

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: dm-crypt: don't modify the data when using authenticated encryption It was said that authenticated encryption could produce invalid tag when the data that is being encrypted is modified [1]. So, fix this problem by copying the data into the clone bio first and then encrypt them inside the clone bio. This may reduce performance, but it is needed to prevent the user from corrupting the device by writing data with O_DIRECT and modifying them at the same time. [1] https://lore.kernel.org/all/20240207004723.GA35324@sol.localdoma...

CVSS
7.1
EPSS
0.28%
20.4% percentile
CISA KEV
Not listed
Published
2024.04.04
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.28%
Technical severityCVSS 7.1

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: dm-crypt: don't modify the data when using authenticated encryption It was said that authenticated encryption could produce invalid tag when the data that is being encrypted is modified [1]. So, fix this problem by copying the data into the clone bio first and then encrypt them inside the clone bio. This may reduce performance, but it is needed to prevent the user from corrupting the device by writing data with O_DIRECT and modifying them at the same time. [1] https://lore.kernel.org/all/20240207004723.GA35324@sol.localdoma...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < 43a202bd552976497474ae144942e32cc5f34d7e, >= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < 0dccbb93538fe89a86c6de31d4b1c8c560848eaa, >= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < 3c652f6fa1e1f9f02c3fbf359d260ad153ec5f90, >= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < 1a4371db68a31076afbe56ecce34fbbe6c80c529, >= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < e08c2a8d27e989f0f5b0888792643027d7e691e6, >= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < 64ba01a365980755732972523600a961c4266b75, >= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < d9e3763a505e50ba3bd22846f2a8db99429fb857, >= ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 < 50c70240097ce41fe6bce6478b80478281e4d0f7, >= 4.12, < 4.19.308, >= 4.20 < 5.4.270, >= 5.5 < 5.10.211, >= 5.11 < 5.15.150, >= 5.16 < 6.1.80, >= 6.2 < 6.6.19, >= 6.7 < 6.7.7, 6.8, 10.0
Fixed versions
4.19.308, 5.4.270, 5.10.211, 5.15.150, 6.1.80, 6.6.19, 6.7.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux 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:N/I:H/A:H
CWE
CWE-787