libcamera: v4l2_videodevice: Handle unexpected buffers

A kernel bug can lead to unexpected buffers being dequeued where we
haven't entered the buffer in our queuedBuffers_ list.

This causes invalid accesses if not handled correctly within libcamera,
and while it is a kernel issue, we must protect against unpatched
kernels.

Handle unexpected buffers by returning a nullptr, and move cache
management after the validation of the buffer.

Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Change-Id: I8c8e0b72a2e529589a1e68b4bcd25bb11c261879

1 files changed, 20 insertions, 1 deletions

diff --git a/src/libcamera/v4l2_videodevice.cpp b/src/libcamera/v4l2_videodevice.cpp
index da2af6a1..33cd9fa4 100644
--- a/src/libcamera/v4l2_videodevice.cpp
+++ b/src/libcamera/v4l2_videodevice.cpp
@@ -1519,9 +1519,28 @@ FrameBuffer *V4L2VideoDevice::dequeueBuffer()
 
 	LOG(V4L2, Debug) << "Dequeuing buffer " << buf.index;
 
+	auto it = queuedBuffers_.find(buf.index);
+	/*
+	 * If the video node fails to stream-on successfully (which can occur
+	 * when queuing a buffer), a vb2 kernel bug can lead to the buffer which
+	 * returns a failure upon queuing, being mistakenly kept in the kernel.
+	 * This leads to the kernel notifying us that a buffer is available to
+	 * dequeue, which we have no awareness of being queued, and thus we will
+	 * not find it in the queuedBuffers_ list.
+	 *
+	 * Whilst this is a kernel bug and should be fixed there, ensure that we
+	 * safely ignore buffers which are unexpected to prevent crashes on
+	 * unpatched kernels.
+	 */
+	if (it == queuedBuffers_.end()) {
+		LOG(V4L2, Error)
+			<< "Dequeued an unexpected buffer: " << buf.index;
+
+		return nullptr;
+	}
+
 	cache_->put(buf.index);
 
-	auto it = queuedBuffers_.find(buf.index);
 	FrameBuffer *buffer = it->second;
 	queuedBuffers_.erase(it);