Linux Kernel up to 5.17.1 smtcfb_write memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Linux Kernel up to 5.17.1. This impacts the function smtcfb_write. Performing a manipulation results in memory corruption.
This vulnerability is identified as CVE-2022-49162. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.17.1. This affects the function smtcfb_write. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: video: fbdev: sm712fb: Fix crash in smtcfb_write() When the sm712fb driver writes three bytes to the framebuffer, the driver will crash: BUG: unable to handle page fault for address: ffffc90001ffffff RIP: 0010:smtcfb_write+0x454/0x5b0 Call Trace: vfs_write+0x291/0xd60 ? do_sys_openat2+0x27d/0x350 ? __fget_light+0x54/0x340 ksys_write+0xce/0x190 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae Fix it by removing the open-coded endianness fixup-code.
It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-49162 since 02/26/2025. The exploitability is told to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/16/2025).
Upgrading to version 4.9.311, 4.14.276, 4.19.238, 5.4.189, 5.10.110, 5.15.33, 5.16.19 or 5.17.2 eliminates this vulnerability. Applying the patch fb791514acf9070225eed46e1ccbb0aa7aae5da5/0ec746674296c94137f074309c26d17e644c0498/1aea36a62f0a0ad67eccc945bac0bd6422ef720f/3b36c05f68ba32d0dfb63abc9016d6fe9117829f/b1c28577529cdfad40c8242673285f1e1e4c314e/eae90015d10f0c9a47fc4adccba4cd79dce664e4/aeb635b49530b7d19e140949753409f759ba99be/809b8cde86320698661eec677222bc5c5df76176/4f01d09b2bbfbcb47b3eb305560a7f4857a32260 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-55063). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 4.9.310
- 4.14.275
- 4.19.237
- 5.4.188
- 5.10.109
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.16.0
- 5.16.1
- 5.16.2
- 5.16.3
- 5.16.4
- 5.16.5
- 5.16.6
- 5.16.7
- 5.16.8
- 5.16.9
- 5.16.10
- 5.16.11
- 5.16.12
- 5.16.13
- 5.16.14
- 5.16.15
- 5.16.16
- 5.16.17
- 5.16.18
- 5.17.0
- 5.17.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 4.9.311/4.14.276/4.19.238/5.4.189/5.10.110/5.15.33/5.16.19/5.17.2
Patch: fb791514acf9070225eed46e1ccbb0aa7aae5da5/0ec746674296c94137f074309c26d17e644c0498/1aea36a62f0a0ad67eccc945bac0bd6422ef720f/3b36c05f68ba32d0dfb63abc9016d6fe9117829f/b1c28577529cdfad40c8242673285f1e1e4c314e/eae90015d10f0c9a47fc4adccba4cd79dce664e4/aeb635b49530b7d19e140949753409f759ba99be/809b8cde86320698661eec677222bc5c5df76176/4f01d09b2bbfbcb47b3eb305560a7f4857a32260
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
10/16/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49162 (🔍)
GCVE (CVE): GCVE-0-2022-49162
GCVE (VulDB): GCVE-100-297471
EUVD: 🔍
Entry
Created: 02/26/2025 11:46Updated: 10/16/2025 02:57
Changes: 02/26/2025 11:46 (58), 10/16/2025 00:31 (1), 10/16/2025 02:57 (12)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.