Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-53113

kernel: wifi: ath11k: fix memory leaks in beacon template setup

Overview

Published
24 Jun 2026
Modified
6 Nov 2026
Medium CVE
0 Registry packages
265 OS packages
10 Linux distributions
Yes Fix available

Description

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

wifi: ath11k: fix memory leaks in beacon template setup

The functions ath11k_mac_setup_bcn_tmpl_ema() and
ath11k_mac_setup_bcn_tmpl_mbssid() allocate memory for beacon templates
but fail to free it when parameter setup returns an error.

Since beacon templates must be released during normal execution, they
must also be released in the error handling paths to prevent memory
leaks.

Fix this by using unified exit paths with proper cleanup in the respective
error paths.

Compile tested only. Issue found using a prototype static analysis tool
and code review.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Weakness: CWE-401

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 57 fixes

Oracle Linux 1 release · 1 package

fixed 1
kernel-uek
Oracle Linux fixes for CVE-2026-53113
ReleasePackageFixed in
9 kernel-uek +34 6.12.0-207.111.5.1.el9uek

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2026-53113
ReleasePackageFixed in
5.0 bpftool +10 6.12.109-1.ph5

Red Hat 1 release · 1 package

affected 1
bpftool
Red Hat fixes for CVE-2026-53113
ReleasePackageFixed in
9 bpftool +105 affected

SUSE Linux Enterprise 1 release · 2 packages

fixed 2
cluster-md-kmp-default kernel-default-base
SUSE Linux Enterprise fixes for CVE-2026-53113
ReleasePackageFixed inAdvisory
16.0 cluster-md-kmp-default +26 6.12.0-160000.37.1 SUSE-SU-2026:23221-1
16.0 kernel-default-base 6.12.0-160000.37.1.160000.2.19 SUSE-SU-2026:23221-1

SUSE Linux Enterprise Micro 1 release · 2 packages

fixed 2
kernel-64kb kernel-default-base
SUSE Linux Enterprise Micro fixes for CVE-2026-53113
ReleasePackageFixed inAdvisory
6.2 kernel-64kb +11 6.12.0-160000.37.1 SUSE-SU-2026:23068-1
6.2 kernel-default-base 6.12.0-160000.37.1.160000.2.19 SUSE-SU-2026:23068-1

chainguard 1 release · 3 packages

not affected 1 fixed 2
linux-gcp-6-18 linux-qemu-melange linux-aws-6-18
chainguard fixes for CVE-2026-53113
ReleasePackageFixed in
linux-gcp-6-18 +1 not affected
linux-qemu-melange 6.18.49-r2
linux-aws-6-18 6.18.54-r1

debian 3 releases · 2 packages

fixed 3
linux-6-12 linux
debian fixes for CVE-2026-53113
ReleasePackageFixed in
12 linux-6-12 6.12.111-1~deb12u1
13 linux 6.12.111-1
14 linux 7.0.10-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2026-53113
ReleasePackageFixed in
linux 6.12.111-1

openSUSE Leap 1 release · 2 packages

fixed 2
cluster-md-kmp-64kb kernel-default-base
openSUSE Leap fixes for CVE-2026-53113
ReleasePackageFixed inAdvisory
16.0 cluster-md-kmp-64kb +74 6.12.0-160000.37.1 openSUSE-SU-2026:21555-1
16.0 kernel-default-base 6.12.0-160000.37.1.160000.2.19 openSUSE-SU-2026:21555-1

ubuntu 3 releases · 34 packages

affected 2 fixed 39
linux-nvidia-6-8 linux-oracle-6-8 linux-ibm-6-8 linux-aws-6-8 linux-azure-fde-6-8 linux-gcp-6-8 +28
ubuntu fixes for CVE-2026-53113
ReleasePackageFixed in
22.04 linux-nvidia-6-8 affected
22.04 linux-oracle-6-8 6.8.0-1067.71~22.04.1
22.04 linux-ibm-6-8 6.8.0-1069.70~22.04.1
22.04 linux-aws-6-8 6.8.0-1069.74~22.04.1
22.04 linux-azure-fde-6-8 6.8.0-1071.78~22.04.1
22.04 linux-gcp-6-8 6.8.0-1073.81~22.04.1

35 more rows

References

Show all 32 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.