Resource Leak Affecting kernel-debuginfo-common-x86_64 package, versions <0:4.14.268-205.500.amzn2


Severity

Recommended
high

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-KERNELDEBUGINFOCOMMONX8664-7708209
  • published20 Aug 2024
  • disclosed16 Jul 2024

Introduced: 16 Jul 2024

CVE-2022-48809  (opens in a new tab)
CWE-402  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade Amazon-Linux:2 kernel-debuginfo-common-x86_64 to version 0:4.14.268-205.500.amzn2 or higher.
This issue was patched in ALAS2-2022-1761.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo-common-x86_64 package and not the kernel-debuginfo-common-x86_64 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:

net: fix a memleak when uncloning an skb dst and its metadata

When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb.

The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak.

Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.

CVSS Scores

version 3.1