netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5e35941d990123f155b02d5663e51a24f816b6f3 · < 6bce72daeccca9aa1746e92d6c3d4784e71f2ebb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case
In decode_int(), the CONS case calls get_bits(bs, 2) to read a length value, then calls get_uint(bs, len) without checking that len bytes remain in the buffer. The existing boundary check only validates the 2 bits for get_bits(), not the subsequent 1-4 bytes that get_uint() reads. This allows a malformed H.323/RAS packet to cause a 1-4 byte slab-out-of-bounds read.
Add a boundary check for len bytes after get_bits() and before get_uint().
From the CVE record · Linux
The Linux kernel's nf_conntrack_h323 component does not check that enough buffer data remains before reading a length value in decode_int(). A malformed H.323/RAS packet can trigger a 1–4 byte slab-out-of-bounds read. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with nf_conntrack_h323 should check their installations; affected versions are not specified.