Answer in brief
CVE-2026-74566 records a Unknown severity vulnerability in keys: make keyring key-chunk byte order agree with keyring_diff_objects(). 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.
A CVSS score is not reported in the current record. 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 | >=f771fde82051976a6fc0fd570f8b86de4a92124b <bd0f976ef89dce6db458bf75bc2cf51127becc41 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <7269df3e7fcfa308e6a456305162f7788747bdbd || >=f771fde82051976a6fc0fd570f8b86de4a92124b <3d9f16c0b643ceac305526b2e2fe25c2c6166926 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <7e5397a3fed0dee7779bd084bec3c0584db3c930 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <58565eef0f8d861aae92abfb7658458d661cee17 | bd0f976ef89dce6db458bf75bc2cf51127becc41, 7269df3e7fcfa308e6a456305162f7788747bdbd, 3d9f16c0b643ceac305526b2e2fe25c2c6166926, 7e5397a3fed0dee7779bd084bec3c0584db3c930, 58565eef0f8d861aae92abfb7658458d661cee17 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: keys: make keyring key-chunk byte order agree with keyring_diff_objects() keyring_get_key_chunk() loads description bytes into the index chunk low address first, while keyring_diff_objects() numbers the first differing bit from the low end and folds the absolute byte index into the level without removing the inline-prefix offset the level already carries. The two disagree on byte order and bit position, so the array can be told two keys first differ at a bit that does not differ in the chunk the walker uses, letting crafted descriptions collide into one node. Load the chunk in the order keyring_diff_objects() assumes and drop the inline-prefix length when folding the byte index into the level. This only changes the in-memory ordering used to place keys within a keyring; add, search and read of non-colliding keys are unaffected.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74566 records a Unknown severity vulnerability in keys: make keyring key-chunk byte order agree with keyring_diff_objects(). 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.
A CVSS score is not reported in the current record. 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 | >=f771fde82051976a6fc0fd570f8b86de4a92124b <bd0f976ef89dce6db458bf75bc2cf51127becc41 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <7269df3e7fcfa308e6a456305162f7788747bdbd || >=f771fde82051976a6fc0fd570f8b86de4a92124b <3d9f16c0b643ceac305526b2e2fe25c2c6166926 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <7e5397a3fed0dee7779bd084bec3c0584db3c930 || >=f771fde82051976a6fc0fd570f8b86de4a92124b <58565eef0f8d861aae92abfb7658458d661cee17 | bd0f976ef89dce6db458bf75bc2cf51127becc41, 7269df3e7fcfa308e6a456305162f7788747bdbd, 3d9f16c0b643ceac305526b2e2fe25c2c6166926, 7e5397a3fed0dee7779bd084bec3c0584db3c930, 58565eef0f8d861aae92abfb7658458d661cee17 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: keys: make keyring key-chunk byte order agree with keyring_diff_objects() keyring_get_key_chunk() loads description bytes into the index chunk low address first, while keyring_diff_objects() numbers the first differing bit from the low end and folds the absolute byte index into the level without removing the inline-prefix offset the level already carries. The two disagree on byte order and bit position, so the array can be told two keys first differ at a bit that does not differ in the chunk the walker uses, letting crafted descriptions collide into one node. Load the chunk in the order keyring_diff_objects() assumes and drop the inline-prefix length when folding the byte index into the level. This only changes the in-memory ordering used to place keys within a keyring; add, search and read of non-colliding keys are unaffected.
Quoted source text, attributed separately from HOL analysis.