Race Condition Affecting kernel-debuginfo-common-aarch64 package, versions <0:6.1.82-99.168.amzn2023


Severity

Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.05% (18th 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-AMZN2023-KERNELDEBUGINFOCOMMONAARCH64-7709190
  • published20 Aug 2024
  • disclosed17 Apr 2024

Introduced: 17 Apr 2024

CVE-2024-26832  (opens in a new tab)
CWE-362  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-debuginfo-common-aarch64 to version 0:6.1.82-99.168.amzn2023 or higher.
This issue was patched in ALAS2023-2024-603.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo-common-aarch64 package and not the kernel-debuginfo-common-aarch64 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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

mm: zswap: fix missing folio cleanup in writeback race path

In zswap_writeback_entry(), after we get a folio from __read_swap_cache_async(), we grab the tree lock again to check that the swap entry was not invalidated and recycled. If it was, we delete the folio we just added to the swap cache and exit.

However, __read_swap_cache_async() returns the folio locked when it is newly allocated, which is always true for this path, and the folio is ref'd. Make sure to unlock and put the folio before returning.

This was discovered by code inspection, probably because this path handles a race condition that should not happen often, and the bug would not crash the system, it will only strand the folio indefinitely.

CVSS Scores

version 3.1