Answer in brief
CVE-2026-43133 records a High severity (CVSS 7.9) vulnerability in KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-43133 records a High severity (CVSS 7.9) vulnerability in KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cc3ed80ae69f454c3d904af9f65394a540099723 <10063e1251c1485034a018236080792ad083dcc5 || >=cc3ed80ae69f454c3d904af9f65394a540099723 <c3b7015000988ba35ecd5648f4b2283960f00543 || >=cc3ed80ae69f454c3d904af9f65394a540099723 <3880e331b0b31d0d5d3702b124f6c93539cd478a || >=cc3ed80ae69f454c3d904af9f65394a540099723 <fce2fd4a2ca05670a91015aacccf96a1c26268fd || >=cc3ed80ae69f454c3d904af9f65394a540099723 <d464cf1ed900d47c85393d40b00017b6adfc2e6c || >=cc3ed80ae69f454c3d904af9f65394a540099723 <0004ecb798b30e90d7ebfe74efae2d9423315a64 || >=cc3ed80ae69f454c3d904af9f65394a540099723 <127ccae2c185f62e6ecb4bf24f9cb307e9b9c619 | 10063e1251c1485034a018236080792ad083dcc5, c3b7015000988ba35ecd5648f4b2283960f00543, 3880e331b0b31d0d5d3702b124f6c93539cd478a, fce2fd4a2ca05670a91015aacccf96a1c26268fd, d464cf1ed900d47c85393d40b00017b6adfc2e6c, 0004ecb798b30e90d7ebfe74efae2d9423315a64, 127ccae2c185f62e6ecb4bf24f9cb307e9b9c619 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state") made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code to always use vmcb01. As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01 instead of the current VMCB.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cc3ed80ae69f454c3d904af9f65394a540099723 <10063e1251c1485034a018236080792ad083dcc5 || >=cc3ed80ae69f454c3d904af9f65394a540099723 <c3b7015000988ba35ecd5648f4b2283960f00543 || >=cc3ed80ae69f454c3d904af9f65394a540099723 <3880e331b0b31d0d5d3702b124f6c93539cd478a || >=cc3ed80ae69f454c3d904af9f65394a540099723 <fce2fd4a2ca05670a91015aacccf96a1c26268fd || >=cc3ed80ae69f454c3d904af9f65394a540099723 <d464cf1ed900d47c85393d40b00017b6adfc2e6c || >=cc3ed80ae69f454c3d904af9f65394a540099723 <0004ecb798b30e90d7ebfe74efae2d9423315a64 || >=cc3ed80ae69f454c3d904af9f65394a540099723 <127ccae2c185f62e6ecb4bf24f9cb307e9b9c619 | 10063e1251c1485034a018236080792ad083dcc5, c3b7015000988ba35ecd5648f4b2283960f00543, 3880e331b0b31d0d5d3702b124f6c93539cd478a, fce2fd4a2ca05670a91015aacccf96a1c26268fd, d464cf1ed900d47c85393d40b00017b6adfc2e6c, 0004ecb798b30e90d7ebfe74efae2d9423315a64, 127ccae2c185f62e6ecb4bf24f9cb307e9b9c619 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state") made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code to always use vmcb01. As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01 instead of the current VMCB.
Quoted source text, attributed separately from HOL analysis.