Upstream information

CVE-2026-43233 at MITRE

Description

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

netfilter: nf_conntrack_h323: fix OOB read in decode_choice()

In decode_choice(), the boundary check before get_len() uses the
variable `len`, which is still 0 from its initialization at the top of
the function:

unsigned int type, ext, len = 0;
...
if (ext || (son->attr & OPEN)) {
BYTE_ALIGN(bs);
if (nf_h323_error_boundary(bs, len, 0)) /* len is 0 here */
return H323_ERROR_BOUND;
len = get_len(bs); /* OOB read */

When the bitstream is exactly consumed (bs->cur == bs->end), the check
nf_h323_error_boundary(bs, 0, 0) evaluates to (bs->cur + 0 > bs->end),
which is false. The subsequent get_len() call then dereferences
*bs->cur++, reading 1 byte past the end of the buffer. If that byte
has bit 7 set, get_len() reads a second byte as well.

This can be triggered remotely by sending a crafted Q.931 SETUP message
with a User-User Information Element containing exactly 2 bytes of
PER-encoded data ({0x08, 0x00}) to port 1720 through a firewall with
the nf_conntrack_h323 helper active. The decoder fully consumes the
PER buffer before reaching this code path, resulting in a 1-2 byte
heap-buffer-overflow read confirmed by AddressSanitizer.

Fix this by checking for 2 bytes (the maximum that get_len() may read)
instead of the uninitialized `len`. This matches the pattern used at
every other get_len() call site in the same file, where the caller
checks for 2 bytes of available data before calling get_len().

SUSE information

Overall state of this security issue: New

This issue is currently rated as having not set severity.

Note from the SUSE Security Team on the kernel-default package

SUSE will no longer fix all CVEs in the Linux Kernel anymore, but declare some bug classes as won't fix. Please refer to TID 21496 for more details.

No SUSE Bugzilla entries cross referenced.

No SUSE Security Announcements cross referenced.

Status of this issue by product and package

Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.

Product(s) Source package State
Products under general support and receiving all security fixes.
SUSE Linux Enterprise Micro 5.3 kernel-default Analysis
SUSE Linux Enterprise Micro 5.3 kernel-source Analysis
SUSE Linux Enterprise Micro 5.3 kernel-source-rt Analysis
SUSE Linux Enterprise Micro 5.4 kernel-default Analysis
SUSE Linux Enterprise Micro 5.4 kernel-source Analysis
SUSE Linux Enterprise Micro 5.4 kernel-source-rt Analysis
Products under Long Term Service Pack support and receiving important and critical security fixes.
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS kernel-default Analysis
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS kernel-source Analysis
SUSE Linux Enterprise Server 12 SP5-LTSS kernel-default Analysis
SUSE Linux Enterprise Server 12 SP5-LTSS kernel-source Analysis
SUSE Linux Enterprise Server 12 SP5-LTSS Extended Security kernel-default Analysis
SUSE Linux Enterprise Server 12 SP5-LTSS Extended Security kernel-source Analysis
SUSE Linux Enterprise Server 15 SP4-LTSS kernel-default Analysis
SUSE Linux Enterprise Server 15 SP4-LTSS kernel-source Analysis
Products past their end of life and not receiving proactive updates anymore.
SUSE Linux Enterprise Server 15 SP3-LTSS kernel-default Analysis
SUSE Linux Enterprise Server 15 SP3-LTSS kernel-source Analysis
SUSE Linux Enterprise Server for SAP Applications 15 SP4 kernel-default Analysis
SUSE Linux Enterprise Server for SAP Applications 15 SP4 kernel-source Analysis

SUSE Timeline for this CVE

CVE page created: Wed May 6 16:06:20 2026
CVE page last modified: Wed May 6 17:29:13 2026