CVE-2024-41066: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-j7w3-jhcq-frvr
Share
CVSS 5.5
CWE-401
Published
Advisory Summary

CVE-2024-41066 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-401: Missing Release of Memory after Effective Lifetime) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.. Remediation is available in the latest vendor maintenance releases.

CVE-2024-41066 at a Glance

CVE Identifier CVE-2024-41066
GHSA Identifier GHSA-j7w3-jhcq-frvr
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-401: Missing Release of Memory after Effective Lifetime
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2024-41066

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2024-41066, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-401: Missing Release of Memory after Effective Lifetime, where the product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Add tx check to prevent skb leak Below is a summary of how the driver stores a reference to an skb during transmit: tx_buff[free_map[consumer_index]]->skb = new_skb; free_map[consumer_index] = IBMVNIC_INVALID_MAP; consumer_index ++; Where variable data looks like this: free_map == [4, IBMVNIC_INVALID_MAP, IBMVNIC_INVALID_MAP, 0, 3] consumer_index^ tx_buff == [skb=null, skb=<ptr>, skb=<ptr>, skb=null, skb=null] The driver has checks to ensure that free_map[consumer_index] pointed to a valid index but there was no check to ensure that this index pointed to an unused/null skb address. So, if, by some chance, our free_map and tx_buff lists become out of sync then we were previously risking an skb memory leak. This could then cause tcp congestion control to stop sending packets, eventually leading to ETIMEDOUT. Therefore, add a conditional to ensure that the skb address is null. If not then warn the user (because this is still a bug that should be patched) and free the old pointer to prevent memleak/tcp problems.

References

git.kernel.org/stable/c/e7b75def33... WEB
https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a
NVD — CVE-2024-41066 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-41066
git.kernel.org/stable/c/0983d288ca... WEB
https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561
git.kernel.org/stable/c/16ad1557ca... WEB
https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c
git.kernel.org/stable/c/267c61c4af... WEB
https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Frequently Asked Questions

What is CVE-2024-41066?
CVE-2024-41066 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-401: Missing Release of Memory after Effective Lifetime.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2024-41066?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2024-41066?
CVE-2024-41066 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2024-41066?
CVE-2024-41066 is classified under CWE-401: Missing Release of Memory after Effective Lifetime (The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.).
How can I check Maven dependencies for CVE-2024-41066?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j7w3-jhcq-frvr",
  "modified" : "2025-11-04T00:31:01Z",
  "published" : "2024-07-29T15:30:44Z",
  "aliases" : [ "CVE-2024-41066" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nibmvnic: Add tx check to prevent skb leak\n\nBelow is a summary of how the driver stores a reference to an skb during\ntransmit:\n    tx_buff[free_map[consumer_index]]->skb = new_skb;\n    free_map[consumer_index] = IBMVNIC_INVALID_MAP;\n    consumer_index ++;\nWhere variable data looks like this:\n    free_map == [4, IBMVNIC_INVALID_MAP, IBMVNIC_INVALID_MAP, 0, 3]\n                                               \tconsumer_index^\n    tx_buff == [skb=null, skb=<ptr>, skb=<ptr>, skb=null, skb=null]\n\nThe driver has checks to ensure that free_map[consumer_index] pointed to\na valid index but there was no check to ensure that this index pointed\nto an unused/null skb address. So, if, by some chance, our free_map and\ntx_buff lists become out of sync then we were previously risking an\nskb memory leak. This could then cause tcp congestion control to stop\nsending packets, eventually leading to ETIMEDOUT.\n\nTherefore, add a conditional to ensure that the skb address is null. If\nnot then warn the user (because this is still a bug that should be\npatched) and free the old pointer to prevent memleak/tcp problems.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-41066"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-401" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2024-07-29T15:15:14Z"
  }
}