CVE-2024-57947: Linux Kernel vulnerability (CVSS 9.8)

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_set_pipapo: fix initial map fill The initial buffer has to be inited to all-ones, but it must restrict it to the size of the first field, not the total field size. After each round in the map search step, the result and the fill map are swapped, so if we have a set where f->bsize of the first element is smaller than m->bsize_max, those one-bits are leaked into future rounds result map. This makes pipapo find an incorrect matching results for sets where first field size is not the largest. Followup patch adds a test case to nft_concat_range.sh selftest script. Thanks to Stefano Brivio for pointing out that we need to zero out the remainder explicitly, only correcting memset() argument isn't enough.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Linux Kernel≥ 5.16 < 6.1.103 · ≥ 5.6 < 5.15.165 · ≥ 6.2 < 6.6.44 · ≥ 6.7 < 6.10.3

Remediation

Fixed in

Linux Kernel≥ 6.1.103

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-57947 being actively exploited?

CVE-2024-57947 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.44%.

How severe is CVE-2024-57947?

CVE-2024-57947 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.44% probability of exploitation.

Which products are affected by CVE-2024-57947?

Affected products include Linux Kernel.

How do I fix CVE-2024-57947?

Upgrade affected software to a fixed version, for example Linux Kernel 6.1.103 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-57947 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo