<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sbin, branch releng/14.3</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F14.3</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F14.3'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2026-04-30T21:21:27Z</updated>
<entry>
<title>dhclient: Improve server and filename validation</title>
<updated>2026-04-30T21:21:27Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2026-04-30T16:45:35Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5bad905eb37f69a8ac90f5e10c07527aded70b5b'/>
<id>urn:sha1:5bad905eb37f69a8ac90f5e10c07527aded70b5b</id>
<content type='text'>
* Don't iterate over each string three times; once is enough.

* Reject control characters (anything below space) in addition to the
  double quote and backslash.

* If an unsafe character is encountered, discard the string instead of
  rejecting the entire lease.

* If backslashes are encountered in the file name option, convert them
  to forward slashes instead of rejecting the option.

* Tweak the warning messages a bit.  Looking through the rest of the
  code, it seems to me that notes generally end with a period while
  warnings generally don't.

Approved by:	so
Security:	FreeBSD-EN-26:11.dhclient
Fixes:		8008e4b88daf ("dhclient: Check for unexpected characters in some DHCP server options")
PR:		294886
MFC after:	1 week
Reviewed by:	brooks, markj
Differential Revision:	https://reviews.freebsd.org/D56740

(cherry picked from commit 873a195ba63575e46686cfd6ea9670a0ca340fa0)
(cherry picked from commit 2f9478ad42c442c49a7eff60227148bf2b90b48c)
</content>
</entry>
<entry>
<title>dhclient: Fix reallocation of dhclient script environments</title>
<updated>2026-04-28T20:33:04Z</updated>
<author>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</author>
<published>2026-04-27T20:56:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=76734958a0986bdd4cf7edfe845b5e7b4e152360'/>
<id>urn:sha1:76734958a0986bdd4cf7edfe845b5e7b4e152360</id>
<content type='text'>
When the number of DHCP options exceeds a threshold, script_set_env()
will reallocate the environment, stored as an array of pointers.  The
calculation of the array size failed to multiply by the pointer size,
resulting in a smaller than expected buffer which admits out-of-bounds
writes.

Approved by:	so
Security:	FreeBSD-SA-26:15.dhclient
Security:	CVE-2026-42511
Reported by:	Joshua Rogers of AISLE Research Team (https://aisle.com/)
</content>
</entry>
<entry>
<title>dhclient: Check for unexpected characters in some DHCP server options</title>
<updated>2026-04-28T20:33:04Z</updated>
<author>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</author>
<published>2026-04-27T20:03:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=dda71167a1013aceb1c4236a9297a24dd62754ac'/>
<id>urn:sha1:dda71167a1013aceb1c4236a9297a24dd62754ac</id>
<content type='text'>
Some options are written directly to the lease file, which may be parsed
by subsequent dhclient invocations.  We must make sure that a malicious
server can't control the "medium" field of a lease definition, otherwise
they can achieve RCE by injecting one into the lease file, whereupon it
will be passed to dhclient-script, which passes it through eval.

Approved by:	so
Security:	FreeBSD-SA-26:12.dhclient
Security:	CVE-2026-42511
Reported by:	Joshua Rogers of AISLE Research Team (https://aisle.com/)
</content>
</entry>
<entry>
<title>pfctl: always warn if a duplicate rule was detected</title>
<updated>2026-03-25T16:13:37Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2026-03-12T14:24:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=926ee630b73d5bf0264bf69284ef4a407b2462d4'/>
<id>urn:sha1:926ee630b73d5bf0264bf69284ef4a407b2462d4</id>
<content type='text'>
Approved by:	so
Security:	FreeBSD-SA-26:09.pf
Security:	CVE-2026-4748
Sponsored by:	Rubicon Communications, LLC ("Netgate")

(cherry picked from commit 66d66dd0f6f83926980fc1d68dd366c0057350c5)
(cherry picked from commit e79818ec36efafc994d8c5a912dcb94986c038c5)
</content>
</entry>
<entry>
<title>route: fix `route -n monitor` when its output is redirected</title>
<updated>2025-08-07T23:22:27Z</updated>
<author>
<name>Oleg Streejak</name>
<email>oleg@pcbtech.ru</email>
</author>
<published>2025-07-17T17:06:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=97f34921d77b62721da53dbde19851cd38efe5c5'/>
<id>urn:sha1:97f34921d77b62721da53dbde19851cd38efe5c5</id>
<content type='text'>
This is a small oversight in the transition to netlink; the non-netlink
implementation would explicitly flush its stdout as necessary to avoid
apparent long stalls in output when we end up fully-buffered.  Adjust
the netlink implementation to do the same.  This was noticed while
trying to triage failures in the wg-quick script.

Commit message by kevans, patch by author.

PR:		278265
Fixes:		091fec1188929 ("route: switch transport protocol [...]")
Approved by:	so
Security:	FreeBSD-EN-25:14.route

(cherry picked from commit 97b61b22edba74c62adba1d022fb73541aa5ff93)
(cherry picked from commit dd695839efd80fe81143cd6c7a552c30df8448f6)
</content>
</entry>
<entry>
<title>mount.8: Add a single example for single user mode</title>
<updated>2025-04-28T06:01:12Z</updated>
<author>
<name>Alexander Ziaee</name>
<email>ziaee@FreeBSD.org</email>
</author>
<published>2025-04-24T22:04:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b90ff465675a2c70060a50c8cfa7db12914bf627'/>
<id>urn:sha1:b90ff465675a2c70060a50c8cfa7db12914bf627</id>
<content type='text'>
The zfs command to do this is a bit longer and harder to remember. In
the last few releases mount(8) learned how to do this, so lets show it
in the manual.

MFC after:		3 days
Reported by:		Jan Bramkamp &lt;crest+freebsd@rlwinm.de&gt;
Discussed with:		cperciva, emaste
Reviewed by:		mhorne
Approved by:		mhorne (mentor)
Differential Revision:	https://reviews.freebsd.org/D49988

(cherry picked from commit c3e06b23b4174c726d7d0ba131869e4aeee8067d)
</content>
</entry>
<entry>
<title>dhclient: Keep two clocks</title>
<updated>2025-04-23T04:50:31Z</updated>
<author>
<name>Colin Percival</name>
<email>cperciva@FreeBSD.org</email>
</author>
<published>2025-04-08T22:50:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d41725ab43017d8cfca35f09bbae1327656af533'/>
<id>urn:sha1:d41725ab43017d8cfca35f09bbae1327656af533</id>
<content type='text'>
Until July 2024, dhclient kept track of time as seconds-since-epoch as
a time_t.  This was a problem because (a) we wanted sub-second timeouts
and (b) timeouts didn't always do the right thing if the system clock
changed.

Switching to using CLOCK_MONOTONIC and struct timespec fixed those
issues but introduced a new problem: CLOCK_MONOTONIC values were being
intepreted as seconds-since-epoch and written to the dhclient.leases
file, causing confusion with DHCP leases expiring in early 1970.

Attempt to compromise between these by keeping track of both times;
any type within dhclient which is a time_t now refers to seconds past
the epoch, while any struct timespec value is a CLOCK_MONOTONIC time.

PR:	283256
Reviewed by:	dch
Fixes:	f0a38976b01e ("dhclient: Use clock_gettime() instead of time()")
Sponsored by:	Amazon
Differential Revision:	https://reviews.freebsd.org/D49720

(cherry picked from commit 43d19e6a4c42ade0f276ceca18a09e2e3829fce4)
</content>
</entry>
<entry>
<title>pfctl: also remove incorrect counter print for rule anchors</title>
<updated>2025-04-21T20:25:46Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2025-04-15T11:13:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=461b79d8ee58fadda788dbf49896bdd027598596'/>
<id>urn:sha1:461b79d8ee58fadda788dbf49896bdd027598596</id>
<content type='text'>
Just as for nat anchors we can't print counters for rule anchors. Remove the
incorrect print call.

MFC after:	2 weeks
Sponsored by:	Rubicon Communications, LLC ("Netgate")

(cherry picked from commit 0fc3c29fb3dd6ab6436a78c502544ebf2cf63ee2)
</content>
</entry>
<entry>
<title>pfctl: fix crash on "pfctl -a '*' -vvsr"</title>
<updated>2025-04-21T20:25:46Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2025-04-14T16:41:00Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a60eeb4331e5ee63f66e2458a16aae186168923f'/>
<id>urn:sha1:a60eeb4331e5ee63f66e2458a16aae186168923f</id>
<content type='text'>
When printing a nat anchor we don't have rule information, or rule
counters. Do not attempt to print them. The information is nonsensical
anyway, and this can cause a crash converting the timestamp to a string,
as years in the very distant future use more digits, and we exceed the
30 byte buffer allocated for this.

MFC after:	2 weeks
Sponsored by:	Orange Business Services

(cherry picked from commit 168d873ae41fd8bd40555322a79c9f215cb4cb9c)
</content>
</entry>
<entry>
<title>msdosfs manuals: Improve visibility and linking</title>
<updated>2025-04-20T00:44:27Z</updated>
<author>
<name>Alexander Ziaee</name>
<email>ziaee@FreeBSD.org</email>
</author>
<published>2024-12-18T18:06:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a516440afdd342fef9925680d890117d6d9024ed'/>
<id>urn:sha1:a516440afdd342fef9925680d890117d6d9024ed</id>
<content type='text'>
+ add `(FAT)` to all descriptions to enable `apropos fat`
+ xref all msdosfs(4) utilities in base to msdosfs(4)
+ xref msdosfs(4) to all msdosfs(4) utilities
+ remove unrelated fsck_ffs(8) from fsck_msdos(8)

MFC after:	3 days
Reviewed by:	mhorne
Approved by:	mhorne (mentor)
Pull Request:	https://github.com/freebsd/freebsd-src/pull/1557

(cherry picked from commit 93f4377caba08e4a47fb9f1878bf609bd4181564)
</content>
</entry>
</feed>
