tty: n_gsm: fix possible out-of-bounds in gsm0_receive()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0fb736c9931e02dbc7d9a75044c8e1c039e50f04, Kernel 46f52c89a7e7d2691b97a9728e4591d071ca8abc, Kernel 47388e807f85948eefc403a8a5fdc5b406a65d5a and 6 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.35, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <0fb736c9931e02dbc7d9a75044c8e1c039e50f04, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <46f52c89a7e7d2691b97a9728e4591d071ca8abc, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <47388e807f85948eefc403a8a5fdc5b406a65d5a, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <4c267110fc110390704cc065edb9817fdd10ff54, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <774d83b008eccb1c48c14dc5486e7aa255731350, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <9513d4148950b05bc99fa7314dc883cc0e1605e5, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <b229bc6c6ea9fe459fc3fa94fd0a27a2f32aca56, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <b890d45aaf02b564e6cae2d2a590f9649330857d, >=e1eaea46bb4020b38a141b84f88565d4603f8dd0 <f126ce7305fe88f49cdabc6db4168b9318898ea3 | 0fb736c9931e02dbc7d9a75044c8e1c039e50f04, 46f52c89a7e7d2691b97a9728e4591d071ca8abc, 47388e807f85948eefc403a8a5fdc5b406a65d5a, 4c267110fc110390704cc065edb9817fdd10ff54, 774d83b008eccb1c48c14dc5486e7aa255731350, 9513d4148950b05bc99fa7314dc883cc0e1605e5, b229bc6c6ea9fe459fc3fa94fd0a27a2f32aca56, b890d45aaf02b564e6cae2d2a590f9649330857d, f126ce7305fe88f49cdabc6db4168b9318898ea3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket