CVE-2026-46033: crypto: authencesn - reject short ahash digests during instance creation
In the Linux kernel, the following vulnerability has been resolved:
crypto: authencesn - reject short ahash digests during instance creation
authencesn requires either a zero authsize or an authsize of at least
4 bytes because the ESN encrypt/decrypt paths always move 4 bytes of
high-order sequence number data at the end of the authenticated data.
While crypto_authenc_esn_setauthsize() already rejects explicit
non-zero authsizes in the range 1..3, crypto_authenc_esn_create()
still copied auth->digestsize into inst->alg.maxauthsize without
validating it. The AEAD core then initialized the tfm's default
authsize from that value.
As a result, selecting an ahash with digest size 1..3, such as
cbcmac(cipher_null), exposed authencesn instances whose default
authsize was invalid even though setauthsize() would have rejected the
same value. AF_ALG could then trigger the ESN tail handling with a
too-short tag and hit an out-of-bounds access.
Reject authencesn instances whose ahash digest size is in the invalid
non-zero range 1..3 so that no tfm can inherit an unsupported default
authsize.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel’s authenticated-encryption handling can let a low-privileged local process cause an out-of-bounds memory access. Successful abuse could expose sensitive kernel memory or crash the system. It is not described as remotely exploitable, and the supplied sources provide no evidence of active exploitation.
Executive priority
Treat this as a high-priority kernel update for shared, multi-user, development, and untrusted-workload systems. Patch through normal emergency maintenance based on vendor confirmation. Single-purpose systems without untrusted local access may have lower immediate exposure, but should still receive the corrected kernel during the next suitable maintenance window.
Technical view
The authencesn implementation accepted an ahash digest size of one to three bytes during instance creation, despite ESN processing always moving four bytes of sequence-number data. This allowed an invalid default authentication size that explicit setauthsize checks would reject. A local AF_ALG caller could reach ESN tail handling with an undersized tag, causing an out-of-bounds access. Stable fixes reject these digest sizes.
Likely exposure
Exposure is most relevant on affected Linux kernels where low-privileged local users or processes can access AF_ALG and instantiate the vulnerable authencesn configuration. Internet exposure alone does not satisfy the stated local attack vector. The supplied version list is insufficient for confidently mapping every distribution kernel or backport.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction. Potential impact includes high confidentiality loss and high availability loss, without stated integrity impact. The CVE is not in KEV, and no supplied source reports active exploitation.
Researcher notes
The flaw is an instance-creation validation gap classified as CWE-1284. The important boundary is a non-zero ahash digest size below four bytes. The source bundle lists multiple stable commits but does not map each commit unambiguously to every affected release or distribution. Avoid assuming vulnerability from version strings alone because vendors commonly backport kernel fixes.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable stable fix referenced for this CVE.
Check distribution advisories for backport status instead of relying only on upstream version numbers.
Prioritize multi-user systems and hosts running untrusted or tenant-controlled local workloads.
Where operationally feasible, restrict unnecessary access to AF_ALG until patching is complete.
Validation and detection
Record each host’s running kernel version, distribution build, and architecture.
Confirm vendor advisories identify the installed kernel package as fixed or unaffected.
Verify the applicable upstream stable commit is present when maintaining custom kernels.
Identify whether untrusted local users or workloads can access AF_ALG.
After updating, confirm hosts booted into the remediated kernel rather than an older installed kernel.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1284: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
12Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1284 · source CWE mapping
Improper Validation of Specified Quantity in Input
Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.