security/certmonger: Fix hardcoded paths
The location of the IPA configuration is hardcoded in three source
files, so on FreeBSD certmonger never finds it and every certificate
request fails with "Unable to determine location of IPA LDAP server".
Renewal is affected too, dogtag-ipa-renew-agent-submit carries the same
paths.
PR: 297709
Approved by: crees (maintainer)
Sponsored by: Netzkommune GmbH
[lldb][lldb-server] Fix compilation on 32-bit (#217934)
Fixes #217348 / a132493da2f60a08cc66c75fa0dd12ccb3fe9c26
NativeProcessProtocol.cpp:679:53:
error: non-constant-expression cannot be narrowed from type 'unsigned
long long' to 'size_t' (aka 'unsigned int') in initializer list
[-Wc++11-narrowing]
679 | const size_t to_write = std::min(size, size_t{sbp_addr - addr});
| ^~~~~~~~~~~~~~~
On 32-bit, size_t is 32-bit but addr_t is still a 64-bit type.
sbp_addr and addr are addr_t, so it makes more sense to cast size to
that. Which is a widening on 32-bit and a nop on 64-bit.
[libc] Avoid add_with_carry name shadowing issue (#215815)
Use fully namespace-qualified calls to the scalar versions of
`add_with_carry` in `big_int.h` to avoid build errors due to
function-name shadowing issues on MSVC when it is configured
without using 2-phase lookup for templates.
This disambiguates the 2 templated functions:
- `add_with_carry(dst, rhs)` in the `multiword` namespace
- `add_with_carry(a, b, carry_in, carry_out)` in the outer libc
namespace
chromium: update to 151.0.7922.173
* 151.0.7922.173
This update includes 7 security fixes. Please see the Chrome Security Page for more information.
[N/A][522819252] Critical CVE-2026-76017: Use after free in Chromoting. Reported by Google on 2026-06-11
[N/A][513757918] High CVE-2026-76018: Privilege elevation in Import. Reported by Google on 2026-05-16
[TBD][539032888] High CVE-2026-76019: Incorrect authorization in Workers. Reported by Anonymous on 2026-07-26
[TBD][541837151] High CVE-2026-76020: Race condition in V8. Reported by Salvatore Gulizia (nickname: Serotav) on 2026-08-03
[N/A][541854084] High CVE-2026-76021: Use after free in DOM. Reported by Google BigSleep at Grape on 2026-08-02
[TBD][543798025] High CVE-2026-76022: Buffer overflow in Network. Reported by 0xAlessandro on 2026-08-07
[TBD][545124048] High CVE-2026-76023: Improper resource control in Linux Toolkit Theming. Reported by Keita Sode and Daisuke Hatakeyama of SYZD Research on 2026-08-11
* 151.0.7922.169
This update includes 15 security fixes. Please see the Chrome Security Page for more information.
[N/A][534923522] Critical CVE-2026-76034: Buffer overflow in WebGL. Reported by Google on 2026-07-15
[N/A][540087398] Critical CVE-2026-76036: Buffer overflow in Dawn. Reported by Google on 2026-07-28
[N/A][516715010] High CVE-2026-76033: Inappropriate implementation in CORS. Reported by Google on 2026-05-26
[12 lines not shown]
vchiq: Merge two commits from Linux
6e474d8e3981 ("staging: vchiq_shim: avoid code duplication") refactors
some code which makes applying the subsequent patch easier.
49bec49fd7f2 ("staging: vc04_services: remove vchiq_copy_from_user")
addresses a user-triggerable integer overflow via the
VCHIQ_IOC_QUEUE_MESSAGE ioctl on /dev/vchiq (which has mode 0600 by
default). It also addresses insufficient validation of user-controlled
addresses in vchiq_copy_from_user().
Update the bcm2835_audio driver to follow the change to
vchi_msg_queue().
Reported by: Vicki Pfau
Reviewed by: Abdelkader Boudih <freebsd at seuros.com>
Tested by: Abdelkader Boudih <freebsd at seuros.com>
Tested by: Marco Devesas Campos <devesas.campos at gmail.com>
MFC after: 2 weeks
[2 lines not shown]
[mlir][ArmNeon] Enable native I8MM integration testing on Darwin (#216098)
This PR, which follows the #215296 fashion, _simply_ allows I8MM tests
to be run natively on Darwin.
**Stacked on** #215296.
---------
Signed-off-by: Federico Bruzzone <federico.bruzzone.i at gmail.com>
libusb: Add an XXX comment for possible duplicate callback IDs
If next_callback_id wraps we could end up with two callbacks with the
same ID. I recommitted the original change despite this issue in order
to fix the libusb API as soon as possible after SHLIB_MAJOR was bumped
in commit 527a82474cb3 (libusb: versioning symbols).
It's very unlikely in practice that software will register and
deregister a sufficient number of callbacks to trigger this, but it is
a real issue to be fixed in a subsequent commit.
Sponsored by: The FreeBSD Foundation
libusb: change callback register handler to int
libusb upstream uses int for register handler. This causes some library
user (like pyusb) to assume that we have int in all implementations and
therefore provides a 4 byte storage only. This causes Segmentation
fault as we will right the pointer.
Reviewed by: adrian
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D54211
(cherry picked from commit ce9ced951a0b9d004a3b007d4ac6e9087a1301a2)
[MLIR][OpenMP] Add verifier to prevent illegal omp.critical nesting (#217357)
This PR adds missing verification to `omp.critical` to prevent illegal
nesting of critical sections. Previously, the missing check allowed
invalid OpenMP programs to compile successfully.
Fixes #217354
Changes:
- Added a verifier check to CriticalOp to ensure it is not illegally
nested within another CriticalOp with the same name.
- Added mlir-opt expected-error tests to catch the malformed IR.
@tblah, @skatrak: Requesting a review for this OpenMP verifier addition.
Co-authored-by: Aidan Dakhama <adakhama at ed.ac.uk>
[libc++] Avoid more <format> code in <vector> (#185596)
This patch primarily splits `__parser` into a `__parser_data` base
class, which contains the actual member variables, and `__parser`, which
just contains the functions operating on the data. This allows us to
store `__parser_data` inside `formatter<bool>` and avoid including most
of the `<format>` code.
This makes it ~45% faster to parse `<vector>` on my system.
Add -use-fortran-assign-only fallback test for both assign paths
Verify that the -use-fortran-assign-only flag forces both the
allocatable and non-allocatable array paths to use _FortranAAssign
instead of _FortranAAssignSimple, preventing regression of the
fallback logic.
Co-Authored-By: Claude Opus 4 (1M context) <noreply at anthropic.com>