sched: sch_cake: fix bulk flow accounting logic for host fairness
In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when iterating through flows. The count of active bulk flows is updated whenever a flow changes state. This has a peculiar interaction with the hash collision handling: when a hash collision occurs (after the set-associative hashing), the state of the hash bucket is simply updated to match the new packet that collided, and if host fairness is enabled, that also means assigning new per-host state to the flow. For this reason, the bulk flow counters of the host(s) assigned to the flow are decremented, before new state is assigned (and the counters, which may not belong to the same host anymore, are incremented again). Back when this code was introduced, the host fairness mode was always enabled, so the decrement was unconditional. When the configuration flags were introduced the *increment* was made conditional, but the *decrement* was not. Which of course can lead to a spurious decrement (and associated wrap-around to U16_MAX). AFAICT, when host fairness is disabled, the decrement and wrap-around happens as soon as a hash collision occurs (which is not that common in itself, due to the set-associative hashing). However, in most cases this is harmless, as the value is only used when host fairne
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.226, 5.15.167, 5.4.284, 6.1.110, 6.10.10, 6.6.51
- CVEs
- CVE-2024-46828
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:16 UTC · Revision 1
Source evidence
sched: sch_cake: fix bulk flow accounting logic for host fairness
core-osv · Original sourcePublished 27 Sept 2024, 12:39 UTC
In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when iterating through flows. The count of active bulk flows is updated whenever a flow changes state. This has a peculiar interaction with the hash collision handling: when a hash collision occurs (after the set-associative hashing), the state of the hash bucket is simply updated to match the new packet that collided, and if host fairness is enabled, that also means assigning new per-host state to the flow. For this reason, the bulk flow counters of the host(s) assigned to the flow are decremented, before new state is assigned (and the counters, which may not belong to the same host anymore, are incremented again). Back when this code was introduced, the host fairness mode was always enabled, so the decrement was unconditional. When the configuration flags were introduced the *increment* was made conditional, but the *decrement* was not. Which of course can lead to a spurious decrement (and associated wrap-around to U16_MAX). AFAICT, when host fairness is disabled, the decrement and wrap-around happens as soon as a hash collision occurs (which is not that common in itself, due to the set-associative hashing). However, in most cases this is harmless, as the value is only used when host fairne
osv:CVE-2024-46828
Kernel
Fixed versions: 5.4.284, 5.10.226, 5.15.167, 6.1.110, 6.6.51, 6.10.10
Complete source record
{
"id": "7aef734e8c34b58a61f8dfec353de4d3b398f5c8364aafb115b2987478a628e8",
"url": "https://osv.dev/vulnerability/CVE-2024-46828",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "sched: sch_cake: fix bulk flow accounting logic for host fairness",
"summary": "In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when iterating through flows. The count of active bulk flows is updated whenever a flow changes state. This has a peculiar interaction with the hash collision handling: when a hash collision occurs (after the set-associative hashing), the state of the hash bucket is simply updated to match the new packet that collided, and if host fairness is enabled, that also means assigning new per-host state to the flow. For this reason, the bulk flow counters of the host(s) assigned to the flow are decremented, before new state is assigned (and the counters, which may not belong to the same host anymore, are incremented again). Back when this code was introduced, the host fairness mode was always enabled, so the decrement was unconditional. When the configuration flags were introduced the *increment* was made conditional, but the *decrement* was not. Which of course can lead to a spurious decrement (and associated wrap-around to U16_MAX). AFAICT, when host fairness is disabled, the decrement and wrap-around happens as soon as a hash collision occurs (which is not that common in itself, due to the set-associative hashing). However, in most cases this is harmless, as the value is only used when host fairne",
"evidence": "osv:CVE-2024-46828",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.284",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.226",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.167",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.110",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.51",
"evidence": "/affected/1/ranges"
},
{
"value": "6.10.10",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-46828",
"aliases": [
"CVE-2024-46828"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "712639929912c5eefb09facccb48d55b3f72c9f8"
},
{
"fixed": "4a4eeefa514db570be025ab46d779af180e2c9bb"
},
{
"fixed": "7725152b54d295b7da5e34c2f419539b30d017bd"
},
{
"fixed": "cde71a5677971f4f1b69b25e854891dbe78066a4"
},
{
"fixed": "549e407569e08459d16122341d332cb508024094"
},
{
"fixed": "d4a9039a7b3d8005b90c7b1a55a306444f0e5447"
},
{
"fixed": "d7c01c0714c04431b5e18cf17a9ea68a553d1c3c"
},
{
"fixed": "546ea84d07e3e324644025e2aae2d12ea4c5896e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-46828.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.1.0"
},
{
"fixed": "5.4.284"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.226"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.167"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.51"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.10.10"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-46828.json"
}
}
],
"modified": "2026-10-28T02:30:24.645498466Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/4a4eeefa514db570be025ab46d779af180e2c9bb",
"https://git.kernel.org/stable/c/546ea84d07e3e324644025e2aae2d12ea4c5896e",
"https://git.kernel.org/stable/c/549e407569e08459d16122341d332cb508024094",
"https://git.kernel.org/stable/c/7725152b54d295b7da5e34c2f419539b30d017bd",
"https://git.kernel.org/stable/c/cde71a5677971f4f1b69b25e854891dbe78066a4",
"https://git.kernel.org/stable/c/d4a9039a7b3d8005b90c7b1a55a306444f0e5447",
"https://git.kernel.org/stable/c/d7c01c0714c04431b5e18cf17a9ea68a553d1c3c",
"https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/46xxx/CVE-2024-46828.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-46828",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/46xxx/CVE-2024-46828.json"
}
},
"related_cves": [
{
"value": "CVE-2024-46828",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490796,
"published_at": "2024-09-27T12:39:27.1+00:00"
}