CVE-2024-36016
In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() Assuming the following: - side A configures the n_gsm in basic option mode - side B sends the header of a basic option mode frame with data length 1 - side A switches to advanced option mode - side B sends 2 data bytes which exceeds gsm->len Reason: gsm->len is not used in advanced option mode. - side A switches to basic option mode - side B keeps sending until gsm0_receive() writes past gsm->buf Reason: Neither gsm->state nor gsm->len have been reset after reconfiguration. Fix this by changing gsm->count to gsm->len comparison from equal to less than. Also add upper limit checks against the constant MAX_MRU in gsm0_receive() and gsm1_receive() to harden against memory corruption of gsm->len and gsm->mru. All other checks remain as we still need to limit the data according to the user configuration and actual payload size.
- Affected products
- Almalinux, Astra Linux, Centos, Linuxmint, Linux Kernel, Red Hat, Red Os, Rocky Linux
- Linux Linux Kernel
- < 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3
- CVSS 3.1
- 7.8 HIGH
- EPSS
- 0.3% (18th percentile)
- Weakness
- CWE-125
- NVD status
- Modified
- Published
- 2024-05-29
No indexed exploits for CVE-2024-36016 yet
Our index is partial: it proves presence, never absence
No exploit for CVE-2024-36016 has been indexed yet. Our index is built from live traffic and upstream syncs, so this page can only say what it knows — not that no exploit exists.