LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46019: crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup

In the Linux kernel, the following vulnerability has been resolved: crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup atmel_aes_buff_init() allocates 4 pages using __get_free_pages() with ATMEL_AES_BUFFER_ORDER, but atmel_aes_buff_cleanup() frees only the first page using free_page(), leaking the remaining 3 pages. Use free_pages() with ATMEL_AES_BUFFER_ORDER to fix the memory leak.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-46019 is a Linux kernel memory leak in the Atmel AES crypto driver. Cleanup code freed only one page after allocating four, leaving three pages leaked. This is most relevant to systems using that driver, especially embedded or hardware-backed crypto deployments.

Executive priority

Treat this as a targeted kernel maintenance issue, not an emergency internet-wide incident. Patch affected embedded or hardware-crypto systems during the next security update window, sooner if they are stability-sensitive or memory constrained.

Technical view

The issue is in atmel_aes_buff_cleanup after atmel_aes_buff_init allocates pages with ATMEL_AES_BUFFER_ORDER. The fix changes cleanup from freeing one page to freeing the full allocation order. Sources describe a kernel memory leak, not memory corruption or privilege escalation.

Likely exposure

Exposure appears limited to Linux kernels carrying the atmel-aes driver and systems where the Atmel AES buffer path is used. General Linux servers without this hardware or driver use may have little practical exposure, but source data does not provide exact platform scope.

Exploitation context

No CISA KEV listing, public exploit claim, or active exploitation evidence is provided. The plausible impact is kernel memory loss over repeated vulnerable cleanup paths, potentially contributing to instability or denial of service. The bundle does not prove attacker reachability.

Researcher notes

The source bundle gives a clear root cause and fix pattern but no CVSS, CWE, exploitability analysis, or trigger conditions. Validation should focus on kernel branch backports and whether atmel-aes is present and operational on the asset.

Mitigation direction

  • Update to a kernel or distro package containing the referenced stable fix.
  • Check vendor kernel advisories for your exact branch and platform.
  • Prioritize embedded systems using Atmel AES crypto hardware.
  • Monitor kernel memory pressure on exposed systems until patched.
  • Avoid direct wrangler-style deploy assumptions; follow vendor update guidance only.

Validation and detection

  • Inventory kernels and identify systems using the atmel-aes driver.
  • Confirm the relevant stable fix commit is present in deployed kernel sources.
  • Review distro changelogs for CVE-2026-46019 backports.
  • Check runtime logs for memory pressure on affected platforms.
  • Document exceptions where the driver or hardware is absent.
Prepared
Confidence
medium
Sources
10

Public sources used

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.

cve · low confidence lookup

CVE-2026-46019 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbbe628ed897d728d38c4035381d12b2f308fac6f, bbe628ed897d728d38c4035381d12b2f308fac6f, bbe628ed897d728d38c4035381d12b2f308fac6f, bbe628ed897d728d38c4035381d12b2f308fac6f, bbe628ed897d728d38c4035381d12b2f308fac6f, bbe628ed897d728d38c4035381d12b2f308fac6f, bbe628ed897d728d38c4035381d12b2f308fac6f, bbe628ed897d728d38c4035381d12b2f308fac6funaffected
LinuxLinux4.5, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.