MontaVista CVE List and Response
MontaVista continually monitors the security community and customers for threats. We follow the community on CVE scoring (NVD) and set fix priority accordingly for affected products. Please view the following CVEs that have been remediated or are in process by clicking the CVE Year to the left or use the CVE Filters below.
For reporting Known Exploitable Vulnerabilities (KEV) or new Security Vulnerabilities, please see our Vulnerability Response Policy or email our PSIRT team. Messages and attachments should be encrypted using PGP and a MontaVista PSIRT PGP key, which is available for download here.
| CVE | Score | Severity | Package | Description | Published |
|---|---|---|---|---|---|
| CVE-2026-35328 |
7.5 (i)
| HIGH | strongswan | ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. | 2026-11-01 |
| CVE-2026-35329 |
7.5 (i)
| HIGH | strongswan | ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. | 2026-11-01 |
| CVE-2026-35330 |
8.1 (i)
| HIGH | strongswan | ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. | 2026-11-01 |
| CVE-2026-35331 |
4.8 (i)
| MEDIUM | strongswan | ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. | 2026-11-01 |
| CVE-2026-35332 |
7.5 (i)
| HIGH | strongswan | ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. | 2026-11-01 |
| CVE-2026-35333 |
7.5 (i)
| HIGH | strongswan | ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. | 2026-11-01 |
| CVE-2026-35334 |
7.5 (i)
| HIGH | strongswan | ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. | 2026-11-01 |
| CVE-2026-99167 |
7.8 (i)
| HIGH | kernel | In the Linux kernel, the following vulnerability has been resolved:net/sched: fix use-after-free in __tcf_action_put()__tcf_action_put() decrements the reference count before decrementing thebinding count. Another thread can free the action between these operations,causing the binding-count update to access freed memory. KASAN reports itas: BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340 Write of size 4 at addr ff11000000d46420 by task tc-put-pause/64Hold the action IDR mutex across both counter updates and IDR removal,keeping cleanup outside the lock. | 2026-10-28 |
| CVE-2026-99143 |
7.8 (i)
| HIGH | kernel | In the Linux kernel, the following vulnerability has been resolved:tracing: Keep the predicate limit separate from program capacitypredicate_parse() adds two to nr_preds to reserve the terminal TRUEand FALSE entries. It also uses that increased value as the limit forparsed predicates. If the initial count is smaller than the numberactually parsed, the program can fill the allocation and subsequentaccesses can go past its end.Keep nr_preds as the predicate limit and use a separate value for theallocation size. This leaves space for both terminal entries and azeroed entry when parsing stops at the limit. | 2026-10-28 |
| CVE-2026-99142 |
7.1 (i)
| HIGH | kernel | In the Linux kernel, the following vulnerability has been resolved:tracing: Check operator stack capacity before pushingpredicate_parse() uses the first operator stack entry before processingany opening parentheses. A push then increments top before writing.The existing check still permits that write when top already points tothe last allocated entry, which can access beyond the operator stack.Reject the push when top reaches the last allocated entry. | 2026-10-28 |