CVE-2022-49886
Last modified
CVE-2022-49886 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Panic on bad configs that #VE on "private" memory access All normal kernel memory is "TDX private memory". This includes everything from kernel stacks to kernel text. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Panic on bad configs that #VE on "private" memory access All normal kernel memory is "TDX private memory". This includes everything from kernel stacks to kernel text. Handling exceptions on arbitrary accesses to kernel memory is essentially impossible because they can happen in horribly nasty places like kernel entry/exit. But, TDX hardware can theoretically _deliver_ a virtualization exception (#VE) on any access to private memory. But, it's not as bad as it sounds. TDX can be configured to never deliver these exceptions on private memory with a "TD attribute" called ATTR_SEPT_VE_DISABLE. The guest has no way to *set* this attribute, but it can check it. Ensure ATTR_SEPT_VE_DISABLE is set in early boot. panic() if it is unset. There is no sane way for Linux to run with this attribute clear so a panic() is appropriate. There's small window during boot before the check where kernel has an early #VE handler. But the handler is only for port I/O and will also panic() as soon as it sees any other #VE, such as a one generated by a private memory access. [ dhansen: Rewrite changelog and rebase on new tdx_parse_tdinfo(). Add Kirill's tested-by because I made changes since he wrote this. ]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.19, < 6.0.8 | — |
| Linux | Linux Kernel | 6.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-49886?
How severe is CVE-2022-49886?
How do I fix CVE-2022-49886?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49880In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49881In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49882In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49883In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-49884In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2022-49885In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49887In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49888In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49889In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4989** UNSUPPORTED WHEN ASSIGNED ** Improper Validation of Speci…8.5
- CVE-2022-49890In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49891In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49886?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
