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 inquiries regarding Security Vulnerabilities, please see our Vulnerability Response Policy or email our PSIRT team security@mvista.com. Email messages and attachments can be encrypted using PGP and a MontaVista PSIRT PGP key, which is available for download here.
| CVE | Score | Severity | Package | Description | Published |
|---|---|---|---|---|---|
| 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-09-04 |
| 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-09-04 |
| 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-09-04 |
| 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-09-04 |
| 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-09-04 |
| 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-09-04 |
| 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-09-02 |
| CVE-2026-72440 |
7.1 (i)
| HIGH | kernel | In the Linux kernel, the following vulnerability has been resolved:md/raid1: fix writes_pending and barrier reference leaks on write failuresraid1_make_request() acquires a writes_pending reference withmd_write_start() before calling raid1_write_request(). Several failurepaths in raid1_write_request() complete the bio and return withoutreaching the normal write completion path, causing the correspondingmd_write_end() to be skipped.Make raid1_write_request() return a status indicating whether the writerequest was successfully queued. This allows raid1_make_request() tocall md_write_end() when raid1_write_request() fails.Additionally, if wait_blocked_rdev() fails after wait_barrier()succeeds, the associated barrier reference is not released.Call allow_barrier() before returning from that path to keep the barrieraccounting balanced. | 2026-08-15 |
| CVE-2026-72439 |
5.5 (i)
| MEDIUM | kernel | In the Linux kernel, the following vulnerability has been resolved:md/raid10: fix writes_pending leak on write request failuresraid10_make_request() acquires a writes_pending reference withmd_write_start() before dispatching write requests. Several failurepaths in raid10_write_request() complete the bio and return withoutreaching the normal write completion path, causing the correspondingmd_write_end() to be skipped.Make raid10_write_request() return a status indicating whether the writerequest was successfully queued. This allows raid10_make_request() torelease the writes_pending reference with md_write_end() when a writerequest fails. | 2026-08-15 |
| CVE-2026-72438 |
7.5 (i)
| HIGH | kernel | In the Linux kernel, the following vulnerability has been resolved:md/raid10: fix writes_pending and barrier reference leaks on discard failuresraid10_make_request() acquires a writes_pending reference withmd_write_start() before calling raid10_handle_discard(). Several failurepaths in raid10_handle_discard() complete the bio and return withoutreleasing the corresponding reference, causing md_write_end() to beskipped.Call md_write_end() before returning from these failure paths to keepwrites_pending accounting balanced.Additionally, discard split allocation failures can occur afterwait_barrier() succeeds. Those paths return without callingallow_barrier(), leaking the associated barrier reference.Release the barrier before returning from those paths. | 2026-08-15 |