Skip to content
Fencer Intel
high 7.8

CVE-2024-26789 json

crypto: arm64/neonbs - fix out-of-bounds access on short input

published 2y ago modified 3mo ago also EUVD-2024-24051

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

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

crypto: arm64/neonbs - fix out-of-bounds access on short input

The bit-sliced implementation of AES-CTR operates on blocks of 128 bytes, and will fall back to the plain NEON version for tail blocks or inputs that are shorter than 128 bytes to begin with.

It will call straight into the plain NEON asm helper, which performs all memory accesses in granules of 16 bytes (the size of a NEON register). For this reason, the associated plain NEON glue code will copy inputs shorter than 16 bytes into a temporary buffer, given that this is a rare occurrence and it is not worth the effort to work around this in the asm code.

The fallback from the bit-sliced NEON version fails to take this into account, potentially resulting in out-of-bounds accesses. So clone the same workaround, and use a temp buffer for short in/outputs.

Patch / fix

  • Linux Linux 6.1.81, 6.6.21, 6.7.9, 6.8
  • linux Debian 12 6.1.82-1
  • linux Debian 14, Debian 13 6.7.9-1

debian advisories DEBIAN-CVE-2024-26789

  • linux-aws-6.5 Ubuntu 22.04 LTS 6.5.0-1023.23~22.04.1
  • linux-gcp-6.5 Ubuntu 22.04 LTS 6.5.0-1024.26~22.04.1
  • linux-hwe-6.5 Ubuntu 22.04 LTS 6.5.0-44.44~22.04.1
  • linux-oem-6.5 Ubuntu 22.04 LTS 6.5.0-1027.28
  • linux-azure-6.5 Ubuntu 22.04 LTS 6.5.0-1024.25~22.04.1
  • linux-nvidia-6.5 Ubuntu 22.04 LTS 6.5.0-1023.24
  • linux-oracle-6.5 Ubuntu 22.04 LTS 6.5.0-1026.26~22.04.1
  • linux-starfive-6.5 Ubuntu 22.04 LTS 6.5.0-1017.18~22.04.1

ubuntu advisories UBUNTU-CVE-2024-26789

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel Azure Linux 3.0 6.6.85.1-1

azure linux advisories AZL-59490

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2024-26789 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-26789 updated cvss 5.5

kernel: crypto: arm64/neonbs - fix out-of-bounds access on short input

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA ADP 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CNA 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.