tracing: Keep the predicate limit separate from program capacity
Impact
In the Linux kernel, the following vulnerability has been resolved:
Source excerpt · LinuxAffected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Linux · Linux
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 39f7c41c908bc82947ce47cdd021520ff486c53f to before 2058a1fe791bb30fd6e4875a7ada3237076c8541 | affected |
| 39f7c41c908bc82947ce47cdd021520ff486c53f to before 68ecc9510bb82dd78585c02bd5357f34ee16b153 | affected |
| 39f7c41c908bc82947ce47cdd021520ff486c53f to before 803aa6fc2dbea25ab9d3ed19eca1c96d0ab17445 | affected |
Linux · Linux
Other versions: affected
| Version / range | Source status |
|---|---|
| 6.6 | affected |
| 0 to before 6.6 | unaffected |
| 6.18.59 through 6.18.* (inclusive) | unaffected |
| 7.2.13 through 7.2.* (inclusive) | unaffected |
| 7.3 through * (inclusive) | unaffected |
Original source description
In the Linux kernel, the following vulnerability has been resolved:
tracing: Keep the predicate limit separate from program capacity
predicate_parse() adds two to nr_preds to reserve the terminal TRUE and FALSE entries. It also uses that increased value as the limit for parsed predicates. If the initial count is smaller than the number actually parsed, the program can fill the allocation and subsequent accesses can go past its end.
Keep nr_preds as the predicate limit and use a separate value for the allocation size. This leaves space for both terminal entries and a zeroed entry when parsing stops at the limit.