Answer in brief
CVE-2024-27414 records a Unknown severity vulnerability in rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back. 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-2024-27414 records a Unknown severity vulnerability in rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back. 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 | >=ad46d4861ed36315d3d9e838723ba3e367ecc042 <b9fbc44159dfc3e9a7073032752d9e03f5194a6f || >=abb0172fa8dc4a4ec51aa992b7269ed65959f310 <882a51a10ecf24ce135d573afa0872aef02c5125 || >=047508edd602921ee8bb0f2aa2100aa2e9bedc75 <a1227b27fcccc99dc44f912b479e01a17e2d7d31 || >=8dfac8071d58447e5cace4c4c6fe493ce2f615f6 <f2261eb994aa5757c1da046b78e3229a3ece0ad9 || >=d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f <167d8642daa6a44b51de17f8ff0f584e1e762db7 || >=d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f <831bc2728fb48a8957a824cba8c264b30dca1425 || >=d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f <743ad091fb46e622f1b690385bb15e3cd3daf874 || 00757f58e37b2d9a6f99e15be484712390cd2bab || >=5.4.253 <5.4.271 || >=5.10.190 <5.10.212 || >=5.15.126 <5.15.151 || >=6.1.45 <6.1.81 || >=6.4.10 <6.5 | b9fbc44159dfc3e9a7073032752d9e03f5194a6f, 882a51a10ecf24ce135d573afa0872aef02c5125, a1227b27fcccc99dc44f912b479e01a17e2d7d31, f2261eb994aa5757c1da046b78e3229a3ece0ad9, 167d8642daa6a44b51de17f8ff0f584e1e762db7, 831bc2728fb48a8957a824cba8c264b30dca1425, 743ad091fb46e622f1b690385bb15e3cd3daf874, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.5 |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
May 17, 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: rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back In the commit d73ef2d69c0d ("rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length"), an adjustment was made to the old loop logic in the function `rtnl_bridge_setlink` to enable the loop to also check the length of the IFLA_BRIDGE_MODE attribute. However, this adjustment removed the `break` statement and led to an error logic of the flags writing back at the end of this function. if (have_flags) memcpy(nla_data(attr), &flags, sizeof(flags)); // attr should point to IFLA_BRIDGE_FLAGS NLA !!! Before the mentioned commit, the `attr` is granted to be IFLA_BRIDGE_FLAGS. However, this is not necessarily true fow now as the updated loop will let the attr point to the last NLA, even an invalid NLA which could cause overflow writes. This patch introduces a new variable `br_flag` to save the NLA pointer that points to IFLA_BRIDGE_FLAGS and uses it to resolve the mentioned error logic.
Quoted source text, attributed separately from HOL analysis.
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 | >=ad46d4861ed36315d3d9e838723ba3e367ecc042 <b9fbc44159dfc3e9a7073032752d9e03f5194a6f || >=abb0172fa8dc4a4ec51aa992b7269ed65959f310 <882a51a10ecf24ce135d573afa0872aef02c5125 || >=047508edd602921ee8bb0f2aa2100aa2e9bedc75 <a1227b27fcccc99dc44f912b479e01a17e2d7d31 || >=8dfac8071d58447e5cace4c4c6fe493ce2f615f6 <f2261eb994aa5757c1da046b78e3229a3ece0ad9 || >=d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f <167d8642daa6a44b51de17f8ff0f584e1e762db7 || >=d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f <831bc2728fb48a8957a824cba8c264b30dca1425 || >=d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f <743ad091fb46e622f1b690385bb15e3cd3daf874 || 00757f58e37b2d9a6f99e15be484712390cd2bab || >=5.4.253 <5.4.271 || >=5.10.190 <5.10.212 || >=5.15.126 <5.15.151 || >=6.1.45 <6.1.81 || >=6.4.10 <6.5 | b9fbc44159dfc3e9a7073032752d9e03f5194a6f, 882a51a10ecf24ce135d573afa0872aef02c5125, a1227b27fcccc99dc44f912b479e01a17e2d7d31, f2261eb994aa5757c1da046b78e3229a3ece0ad9, 167d8642daa6a44b51de17f8ff0f584e1e762db7, 831bc2728fb48a8957a824cba8c264b30dca1425, 743ad091fb46e622f1b690385bb15e3cd3daf874, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.5 |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
May 17, 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: rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back In the commit d73ef2d69c0d ("rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length"), an adjustment was made to the old loop logic in the function `rtnl_bridge_setlink` to enable the loop to also check the length of the IFLA_BRIDGE_MODE attribute. However, this adjustment removed the `break` statement and led to an error logic of the flags writing back at the end of this function. if (have_flags) memcpy(nla_data(attr), &flags, sizeof(flags)); // attr should point to IFLA_BRIDGE_FLAGS NLA !!! Before the mentioned commit, the `attr` is granted to be IFLA_BRIDGE_FLAGS. However, this is not necessarily true fow now as the updated loop will let the attr point to the last NLA, even an invalid NLA which could cause overflow writes. This patch introduces a new variable `br_flag` to save the NLA pointer that points to IFLA_BRIDGE_FLAGS and uses it to resolve the mentioned error logic.
Quoted source text, attributed separately from HOL analysis.