Answer in brief
CVE-2024-44966 records a Unknown severity vulnerability in binfmt_flat: Fix corruption when not offsetting data start. 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 | >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <3a684499261d0f7ed5ee72793025c88c2276809c || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <af65d5383854cc3f172a7d0843b628758bf462c8 || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <49df34d2b7da9e57c839555a2f7877291ce45ad1 || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <9350ba06ee61db392c486716ac68ecc20e030f7c || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <3eb3cd5992f7a0c37edc8d05b4c38c98758d8671 | 3a684499261d0f7ed5ee72793025c88c2276809c, af65d5383854cc3f172a7d0843b628758bf462c8, 49df34d2b7da9e57c839555a2f7877291ce45ad1, 9350ba06ee61db392c486716ac68ecc20e030f7c, 3eb3cd5992f7a0c37edc8d05b4c38c98758d8671 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Sep 4, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: binfmt_flat: Fix corruption when not offsetting data start Commit 04d82a6d0881 ("binfmt_flat: allow not offsetting data start") introduced a RISC-V specific variant of the FLAT format which does not allocate any space for the (obsolete) array of shared library pointers. However, it did not disable the code which initializes the array, resulting in the corruption of sizeof(long) bytes before the DATA segment, generally the end of the TEXT segment. Introduce MAX_SHARED_LIBS_UPDATE which depends on the state of CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET to guard the initialization of the shared library pointer region so that it will only be initialized if space is reserved for it.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-44966 records a Unknown severity vulnerability in binfmt_flat: Fix corruption when not offsetting data start. 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 | >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <3a684499261d0f7ed5ee72793025c88c2276809c || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <af65d5383854cc3f172a7d0843b628758bf462c8 || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <49df34d2b7da9e57c839555a2f7877291ce45ad1 || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <9350ba06ee61db392c486716ac68ecc20e030f7c || >=04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8 <3eb3cd5992f7a0c37edc8d05b4c38c98758d8671 | 3a684499261d0f7ed5ee72793025c88c2276809c, af65d5383854cc3f172a7d0843b628758bf462c8, 49df34d2b7da9e57c839555a2f7877291ce45ad1, 9350ba06ee61db392c486716ac68ecc20e030f7c, 3eb3cd5992f7a0c37edc8d05b4c38c98758d8671 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Sep 4, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: binfmt_flat: Fix corruption when not offsetting data start Commit 04d82a6d0881 ("binfmt_flat: allow not offsetting data start") introduced a RISC-V specific variant of the FLAT format which does not allocate any space for the (obsolete) array of shared library pointers. However, it did not disable the code which initializes the array, resulting in the corruption of sizeof(long) bytes before the DATA segment, generally the end of the TEXT segment. Introduce MAX_SHARED_LIBS_UPDATE which depends on the state of CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET to guard the initialization of the shared library pointer region so that it will only be initialized if space is reserved for it.
Quoted source text, attributed separately from HOL analysis.