CVE-2024-46840 Affecting kernel-livepatch-4.14.355-271.569 package, versions <0:1.0-0.amzn2


Severity

Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.04% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2-KERNELLIVEPATCH414355271569-8382946
  • published16 Nov 2024
  • disclosed27 Sept 2024

Introduced: 27 Sep 2024

CVE-2024-46840  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade Amazon-Linux:2 kernel-livepatch-4.14.355-271.569 to version 0:1.0-0.amzn2 or higher.
This issue was patched in ALAS2-2024-2696.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-4.14.355-271.569 package and not the kernel-livepatch-4.14.355-271.569 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

btrfs: clean up our handling of refs == 0 in snapshot delete

In reada we BUG_ON(refs == 0), which could be unkind since we aren't holding a lock on the extent leaf and thus could get a transient incorrect answer. In walk_down_proc we also BUG_ON(refs == 0), which could happen if we have extent tree corruption. Change that to return -EUCLEAN. In do_walk_down() we catch this case and handle it correctly, however we return -EIO, which -EUCLEAN is a more appropriate error code. Finally in walk_up_proc we have the same BUG_ON(refs == 0), so convert that to proper error handling. Also adjust the error message so we can actually do something with the information.

CVSS Scores

version 3.1