FKIE_CVE-2026-23333

Vulnerability from fkie_nvd - Published: 2026-03-25 11:16 - Updated: 2026-03-25 15:41
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: validate open interval overlap [ Upstream commit 648946966a08e4cb1a71619e3d1b12bd7642de7b ] Open intervals do not have an end element, in particular an open interval at the end of the set is hard to validate because of it is lacking the end element, and interval validation relies on such end element to perform the checks. This patch adds a new flag field to struct nft_set_elem, this is not an issue because this is a temporary object that is allocated in the stack from the insert/deactivate path. This flag field is used to specify that this is the last element in this add/delete command. The last flag is used, in combination with the start element cookie, to check if there is a partial overlap, eg. Already exists: 255.255.255.0-255.255.255.254 Add interval: 255.255.255.0-255.255.255.255 ~~~~~~~~~~~~~ start element overlap Basically, the idea is to check for an existing end element in the set if there is an overlap with an existing start element. However, the last open interval can come in any position in the add command, the corner case can get a bit more complicated: Already exists: 255.255.255.0-255.255.255.254 Add intervals: 255.255.255.0-255.255.255.255,255.255.255.0-255.255.255.254 ~~~~~~~~~~~~~ start element overlap To catch this overlap, annotate that the new start element is a possible overlap, then report the overlap if the next element is another start element that confirms that previous element in an open interval at the end of the set. For deletions, do not update the start cookie when deleting an open interval, otherwise this can trigger spurious EEXIST when adding new elements. Unfortunately, there is no NFT_SET_ELEM_INTERVAL_OPEN flag which would make easier to detect open interval overlaps.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/6db2be971e3d70c9e3f85d39eff7103c2ee2f579
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_rbtree: validate open interval overlap\n\n[ Upstream commit 648946966a08e4cb1a71619e3d1b12bd7642de7b ]\n\nOpen intervals do not have an end element, in particular an open\ninterval at the end of the set is hard to validate because of it is\nlacking the end element, and interval validation relies on such end\nelement to perform the checks.\n\nThis patch adds a new flag field to struct nft_set_elem, this is not an\nissue because this is a temporary object that is allocated in the stack\nfrom the insert/deactivate path. This flag field is used to specify that\nthis is the last element in this add/delete command.\n\nThe last flag is used, in combination with the start element cookie, to\ncheck if there is a partial overlap, eg.\n\n   Already exists:   255.255.255.0-255.255.255.254\n   Add interval:     255.255.255.0-255.255.255.255\n                     ~~~~~~~~~~~~~\n             start element overlap\n\nBasically, the idea is to check for an existing end element in the set\nif there is an overlap with an existing start element.\n\nHowever, the last open interval can come in any position in the add\ncommand, the corner case can get a bit more complicated:\n\n   Already exists:   255.255.255.0-255.255.255.254\n   Add intervals:    255.255.255.0-255.255.255.255,255.255.255.0-255.255.255.254\n                     ~~~~~~~~~~~~~\n             start element overlap\n\nTo catch this overlap, annotate that the new start element is a possible\noverlap, then report the overlap if the next element is another start\nelement that confirms that previous element in an open interval at the\nend of the set.\n\nFor deletions, do not update the start cookie when deleting an open\ninterval, otherwise this can trigger spurious EEXIST when adding new\nelements.\n\nUnfortunately, there is no NFT_SET_ELEM_INTERVAL_OPEN flag which would\nmake easier to detect open interval overlaps."
    }
  ],
  "id": "CVE-2026-23333",
  "lastModified": "2026-03-25T15:41:33.977",
  "metrics": {},
  "published": "2026-03-25T11:16:30.780",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/6db2be971e3d70c9e3f85d39eff7103c2ee2f579"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.