Bugs fixes in "libxslt"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2025-7424 | A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion du | 2026-01-07 |
| CVE | CVE-2025-7424 | A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion du | 2026-01-07 |
| CVE | CVE-2025-7424 | A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion du | 2026-01-07 |
| CVE | CVE-2025-7424 | A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion du | 2026-01-07 |
| CVE | CVE-2025-7424 | A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion du | 2026-01-07 |
| CVE | CVE-2025-7424 | A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion du | 2026-01-07 |
| CVE | CVE-2023-40403 | The issue was addressed with improved memory handling. This issue is fixed in macOS Ventura 13.6, tvOS 17, iOS 16.7 and iPadOS 16.7, macOS Monterey 1 | 2025-06-26 |
| CVE | CVE-2023-40403 | The issue was addressed with improved memory handling. This issue is fixed in macOS Ventura 13.6, tvOS 17, iOS 16.7 and iPadOS 16.7, macOS Monterey 1 | 2025-06-26 |
| CVE | CVE-2025-24855 | numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restore | 2025-03-20 |
| CVE | CVE-2025-24855 | numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restore | 2025-03-20 |
| CVE | CVE-2025-24855 | numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restore | 2025-03-20 |
| CVE | CVE-2025-24855 | numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restore | 2025-03-20 |
| CVE | CVE-2025-24855 | numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restore | 2025-03-20 |
| CVE | CVE-2025-24855 | numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restore | 2025-03-20 |
| CVE | CVE-2024-55549 | xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes. | 2025-03-19 |
| CVE | CVE-2024-55549 | xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes. | 2025-03-19 |
| CVE | CVE-2024-55549 | xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes. | 2025-03-19 |
| CVE | CVE-2024-55549 | xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes. | 2025-03-19 |
| CVE | CVE-2024-55549 | xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes. | 2025-03-19 |
| CVE | CVE-2024-55549 | xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes. | 2025-03-19 |
About
-
Send Feedback to @ubuntu_updates
